[94838] trunk/dports
Ryan Schmidt
ryandesign at macports.org
Tue Jul 3 00:09:49 PDT 2012
On Jul 1, 2012, at 23:59, Anders F Björklund wrote:
> Ryan Schmidt wrote:
>
>>> xz: upgrade to 5.0.4
>>>
>>> Stop splitting the port into a static xz and a shared liblzma,
>>> include everything in the "xz" port like done with bzip2 etc.
>>> Ignore the license and bloat issues that this brings, for now.
>>> Mark the "liblzma" port as being replaced_by the new xz port.
>>
>> I thought it was nice having them split up, especially if liblzma is licensed differently from the xz command line utilities.
>
> I thought so too, but that's not how things are done in MacPorts.
If there are license-related reasons why doing so would be beneficial, then absolutely we should be doing so in MacPorts. It's fairly common for a package to include both command-line utilities under the GPL and libraries under the LGPL. It would be best to have those in separate ports (or probably better yet subports) so that ports that depend on the library don't get unnecessarily constrained by the GPL.
As another example, the pianobar port has a libpiano subport. In this case, it's not a license issue, merely the situation that they're two separate pieces of software, which don't require one another, which the user might install for separate reasons.
> Actually I think the best would be to have liblzma included with
> the system like it is in FreeBSD, but that's not happening and
> MacPorts wouldn't use it anyway like it ignores zlib and bzip2.
> So it's being made available in /usr/local, rather than /usr...
>
> Feel free to hack the configure phase etc of liblzma, bumped rev.
I've fixed liblzma now in r94975. In the future please make sure to follow the recipe or the guide or use the "obsolete" portgroup when replacing ports, so that users don't run into the problems they ran into this time.
On Jul 2, 2012, at 00:04, Anders F Björklund wrote:
> If port can't handle replaced dependencies, I guess they would need
> to be replaced manually (i.e. swapping "liblzma" depends for "xz")
Yes, that is also part of what you need to do when you replace a port.
More information about the macports-dev
mailing list