Opened 6 years ago

Closed 6 years ago

#56287 closed defect (fixed)

Remove py-bob and their modules from macports

Reported by: tiagofrepereira2012 (Tiago Freitas Pereira) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: andre.anjos@…, devans@…, mojca@…
Port: py-bob

Description

Hi,

We have recently adopted conda to distribute Bob. With conda, it easier for us to maintain Bob for both Linux/Mac platforms. Hence, we would like to remove all the Bob modules from Mac Ports.

How should we proceed?

Follow below the list of modules involved and should be deleted.

  • bob
  • py-bob
  • py-bob-ap
  • py-bob-blitz
  • py-bob-core
  • py-bob-db-atnt
  • py-bob-db-base
  • py-bob-db-iris
  • py-bob-db-mnist
  • py-bob-db-verification-utils
  • py-bob-db-wine
  • py-bob-extension
  • py-bob-io-base
  • py-bob-io-image
  • py-bob-io-matlab
  • py-bob-io-video
  • py-bob-ip-base
  • py-bob-ip-color
  • py-bob-ip-draw
  • py-bob-ip-facedetect
  • py-bob-ip-gabor
  • py-bob-ip-optflow-hornschunck
  • py-bob-ip-optflow-liu
  • py-bob-learn-activation
  • py-bob-learn-boosting
  • py-bob-learn-em
  • py-bob-learn-libsvm
  • py-bob-learn-linear
  • py-bob-learn-mlp
  • py-bob-math
  • py-bob-measure
  • py-bob-sp

Thanks

Change History (6)

comment:1 Changed 6 years ago by mojca (Mojca Miklavec)

Just to explain: if you no longer wish to maintain these ports, this doesn't have to be the reason to delete the ports, other users might still find them useful. Having ten different package managers installed on computer is usually a recipe for disaster, and conda cannot serve as a complete replacement for MacPorts just yet. Using conda is fine for users who would have to install MacPorts just for the sake of using your packages, but not for existing users who needs lots of other software from MP.

That said, giving impression of MacPorts providing those packages, while in fact providing outdated and broken Portfiles, doesn't really serve anyone, and it causes lots of broken builds on our buildbot as well.

There are two possible ways to proceed:

  • delete the packages (I still miss some kind of graveyard section of easy-to-find broken packages that can be picked up and improved by users who might need them)
  • someone (not necessarily you) tries to bring those packages up to date, so that they can still serve MacPorts users, even if you recommend a different installation path

I would not be happy to provide outdated/broken packages for another two years. Updating them usually doesn't mean a prohibitive amount of work. This one time one would need to update a bit more bits and pieces because the upstream sources have been moved. But after that it's usually just a matter of changing the version number and checksums which can be accomplished trivially.

comment:2 Changed 6 years ago by mf2k (Frank Schima)

Type: requestenhancement

Note that a "request" ticket type is only for requesting a new port.

comment:3 Changed 6 years ago by tiagofrepereira2012 (Tiago Freitas Pereira)

Dear Mojca,

I spoke with the other maintainers of the ports for Bob and we'll go for the first option (delete the packages).

I'm sorry, but we don't have the time to keep them updated and, as you said, keeping those ports broken serves no purpose.

Thanks

comment:4 Changed 6 years ago by mojca (Mojca Miklavec)

Type: enhancementdefect

Frank, I marked this as bug instead of enhancement because the ports are currently broken. I'll probably create a PR to delete the ports (unless someone steps up to fix the issues).

comment:6 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: set to ryandesign
Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.