Re: Why is Python 2.7 dependent on db46 and only db46
On 2015-7-22 03:43 , Daniel J. Luke wrote: On Jul 21, 2015, at 1:37 PM, Vincent Habchi vi...@macports.org wrote: On 21 Jul 2015, at 19:27, Daniel J. Luke dl...@geeklair.net wrote: IIRC oracle changed the bdb license after 4.6. I have a dim recollection that I was going to try to look over the new license to make sure it was reasonable to update the bdb that apr-util (and subversion) use, but I never got around to it. If someone has looked it over and it’s OK, we should just update everything to whatever the latest (compatible) version is. Wikipedia says db60 is licenced under the GNU AGPL v3. ok, so it went from: Sleepycat to Oracle-modified Sleepycat to AGPL v3 so, my vote would be to move everything to bdb6, then (unless there’s a good reason not to that anyone can think of). The AGPL, being based on the GPL, contains the no further restrictions requirement that makes it incompatible with a number of licenses including OpenSSL's. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
On 21.7.2015, at 20.43, Daniel J. Luke dl...@geeklair.net wrote: so, my vote would be to move everything to bdb6, then (unless there’s a good reason not to that anyone can think of). This makes sense. In updating python27 (which, btw, depends on db48, not db46:) it would probably be a good idea to add a note to keep an eye on bdb new versions, too. ! ! Jyrki ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
On 21 Jul 2015, at 19:27, Daniel J. Luke dl...@geeklair.net wrote: IIRC oracle changed the bdb license after 4.6. I have a dim recollection that I was going to try to look over the new license to make sure it was reasonable to update the bdb that apr-util (and subversion) use, but I never got around to it. If someone has looked it over and it’s OK, we should just update everything to whatever the latest (compatible) version is. Wikipedia says db60 is licenced under the GNU AGPL v3. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
On Jul 21, 2015, at 10:00 AM, Clemens Lang c...@macports.org wrote: - On 21 Jul, 2015, at 15:43, Rainer Müller rai...@macports.org wrote: And even if the default +db* variant selection depends on the local active db* version, I guess such a change would trigger more local builds instead of using binary archives which should be preferred for most users. However, what we could do -- and I'd argue we should -- is choose a single blessed version of db and try to use it everywhere. Normally, that would just be the latest version. IIRC oracle changed the bdb license after 4.6. I have a dim recollection that I was going to try to look over the new license to make sure it was reasonable to update the bdb that apr-util (and subversion) use, but I never got around to it. If someone has looked it over and it’s OK, we should just update everything to whatever the latest (compatible) version is. At least some ports use db46 because apr-util/subversion use it and they want to use the same version. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
On Jul 21, 2015, at 1:37 PM, Vincent Habchi vi...@macports.org wrote: On 21 Jul 2015, at 19:27, Daniel J. Luke dl...@geeklair.net wrote: IIRC oracle changed the bdb license after 4.6. I have a dim recollection that I was going to try to look over the new license to make sure it was reasonable to update the bdb that apr-util (and subversion) use, but I never got around to it. If someone has looked it over and it’s OK, we should just update everything to whatever the latest (compatible) version is. Wikipedia says db60 is licenced under the GNU AGPL v3. ok, so it went from: Sleepycat to Oracle-modified Sleepycat to AGPL v3 so, my vote would be to move everything to bdb6, then (unless there’s a good reason not to that anyone can think of). -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
- On 21 Jul, 2015, at 15:43, Rainer Müller rai...@macports.org wrote: And even if the default +db* variant selection depends on the local active db* version, I guess such a change would trigger more local builds instead of using binary archives which should be preferred for most users. However, what we could do -- and I'd argue we should -- is choose a single blessed version of db and try to use it everywhere. Normally, that would just be the latest version. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
On Tue, Jul 21, 2015 at 10:00 AM, Clemens Lang c...@macports.org wrote: - On 21 Jul, 2015, at 15:43, Rainer Müller rai...@macports.org wrote: And even if the default +db* variant selection depends on the local active db* version, I guess such a change would trigger more local builds instead of using binary archives which should be preferred for most users. However, what we could do -- and I'd argue we should -- is choose a single blessed version of db and try to use it everywhere. Normally, that would just be the latest version. Last I checked, upgrading existing data files was not automatic. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
On 21 Jul 2015, at 16:02, Brandon Allbery allber...@gmail.com wrote: On Tue, Jul 21, 2015 at 10:00 AM, Clemens Lang c...@macports.org wrote: - On 21 Jul, 2015, at 15:43, Rainer Müller rai...@macports.org wrote: And even if the default +db* variant selection depends on the local active db* version, I guess such a change would trigger more local builds instead of using binary archives which should be preferred for most users. However, what we could do -- and I'd argue we should -- is choose a single blessed version of db and try to use it everywhere. Normally, that would just be the latest version. Last I checked, upgrading existing data files was not automatic. And something approaching what we do with perl/python, that is using a generic port as a proxy for a chosen version? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Why is Python 2.7 dependent on db46 and only db46
On 2015-07-21 14:35, Vincent Habchi wrote: In new the port cyrus5-imapd I committed this morning, I wrote some dynamic code to detect the installed db* version and go along with it, instead of forcing the installation of another version. Could this mechanism be extended, maybe though a port class? You could only do this if you wrap the choice in variants. Automatic detection does not work with binary archives. Everything influencing the build must be defined by the canonical combination of name/epoch/version/revision/variants for reproducible builds. And even if the default +db* variant selection depends on the local active db* version, I guess such a change would trigger more local builds instead of using binary archives which should be preferred for most users. Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Why is Python 2.7 dependent on db46 and only db46
Hi there, I recently had a look on the smörgåsbord of ports installed on my computer, and I found out three different versions of db: db44 db46 db48. Turns out a lot of ports have a fixed dependency on one of the db* ports, which in turn implies that a lot of different versions of db4 have to be installed – to no avail, since those ports provide the same service; worse, db5* and the most recent db6* are, it seems, totally ignored. Example of this is Python27 that requires db46, but works fine with db60. In new the port cyrus5-imapd I committed this morning, I wrote some dynamic code to detect the installed db* version and go along with it, instead of forcing the installation of another version. Could this mechanism be extended, maybe though a port class? Thanks, Vincent ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
