bob: update to v2.0

[dbevans (David B. Evans)]

Current MacPorts version of bob is 1.2.2 which is now outdated by the release of bob v2. Considering the new organization of the package perhaps multiple ports are called for.

Release annoucement is ​here.

[dbevans (David B. Evans)]

Any thoughts about this? Should v2 replace v1.2.2 or should they co-exist? Are there any issues with installing v2 on Mac OS X?

[andre.dos.anjos@…]

v2 should replace v1.2.2. Some notes:

1. v2 was conceived so that Bob is distributable via PyPI (that wasn't the case before). It now uses setuptools to build and install. CMake is gone.
2. By breaking it into multiple packages, it can be expected that the release cycle decreases for some of the packages (this means a bit more of work for packagers).

I'd like to hear your opinion about this. Is there a method for easily converting a PyPI/setuptools python package into a MacPorts package?

[dbevans (David B. Evans)]

Replying to andre.dos.anjos@…:

I'd like to hear your opinion about this. Is there a method for easily converting a PyPI/setuptools python package into a MacPorts package?

It's not too hard to do a python port like this by hand. Most of the work is done by the python PortGroup​. See any of the existing py-* ports for examples. Since we support multiple parallel installed versions of python, a python port typically includes subports for each version of python that is supported. Right now, we are trying to whittle the number of python versions supported to something like just python27 and python34 but python26 and python33 are not unheard of as yet. But again this depends on what versions of python your packages support.

Having said that, there IS a tool for making a Portfile from PyPI, pypi2port that you might want to look at. It's fairly new, however, and I see there are a few tickets on the current version so I'm not sure how solid it is as yet.

See #47140, #47141, #47143 and

port info pypi2port

for basic information.

I'm copying the author who can give you the full details.

Just for my curiosity how many different packages are we talking about?

[andre.dos.anjos@…]

What is equivalent to the old Bob is broken down in ~20 packages (​https://raw.githubusercontent.com/idiap/bob/master/dependencies.png). In that drawing, it would correspond to most light-blue boxes.

We're also considering to have a "base" set of Bob packages and package those as a whole instead. Do you see anything against this approach?

[dbevans (David B. Evans)]

Replying to andre.dos.anjos@…:

We're also considering to have a "base" set of Bob packages and package those as a whole instead. Do you see anything against this approach?

Not at all. In fact, it might be more 'user friendly' for new users. As I read your online documentation for the first time, it wasn't clear to me what group of packages were needed to build a minimal functional system and which were optional. In this case you might have a single port bob that installs the base set but includes subports for each of the optional packages.

Port php is an example that does something like this to handle a large collection of php modules.

[tiagofrepereira2012 (Tiago Freitas Pereira)]

Hi @devans,

We developed a port using the python PortGroup. It is called py-bob. Furthermore we deprecated the port called bob

The tickets are opened here #48994 #48995, maybe you can have a look.

Thanks

Tiago

[dbevans (David B. Evans)]

Will take a look, thanks.

[dbevans (David B. Evans)]

Tiago --

I've downloaded the ports from #48994 and have started testing. I've run into a few issues but will comment on theme on that ticket.

[dbevans (David B. Evans)]

Update to py-bob 2.0.6 completed in #48994, #48995. Thanks.