On 2010-5-20 03:58 , Ryan Stonecipher-Fisher wrote:
> On Wed, May 19, 2010 at 03:40,
> <[email protected]> wrote:
>>
>> We have the existing habit of creating ports with version numbers in the
>> name, if older versions are still required by some ports. For example, since
>> hdf4 requires jpeg 6, we could create a new port jpeg6 (svn copy'd from the
>> last version of the jpeg that had version 6) to provide that version of the
>> library and headers.
>
> Could the same style be applied to resurrect the mpeg4ip version of
> libmp4v2 (the version abandoned by its maintainers and forked into the
> current google code mp4v2 project) to fix gtkpod?
Sure.
> The release version of gtkpod still depends upon the old library, and
> its current development trunk is not marked as "release candidate" or
> anything else that would suggest it is stable enough to be unleashed
> on users.
> What should be done if the two libraries have headers or binaries with
> identical filenames?
Normally you'd install the older one into a subdir (e.g. lib/${name} and
include/${name}) and have the dependents use appropriate -I/-L flags. Or
you might get away with renaming the files and having the dependents use
something like -ljpeg6.
- Josh
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
