Bernd,
Thanks for your comments!
> I've made a port for mpd (and also some mpd-clients) already.
I'll > submit it in a few days, so maybe we can join our effords.
That sounds like a good idea. I checked for existing ports, but
didn't find any, that's why I made my own. Maybe you can send me
your ports so I can watch and learn? I'm still relatively new to
the ports system, especially the new features not in the porting
guide.
> $ make lib-depends-check
> /usr/ports/packages/all/mpd-0.11.5.tgz:
> Missing: id3tag.3 (/usr/local/bin/mpd): NOT REACHABLE
> Missing: iconv.4 (/usr/local/bin/mpd): NOT REACHABLE
> Missing: mad.2 (/usr/local/bin/mpd): NOT REACHABLE
I had not included these, because he mpd documentation does not
list these as dependencies. IIRC, mad and id3tag are included in
the distribution, so mpd will compile if these are not present on
the system. I was hoping to get some feedback on what would be the
best way to deal with this; my intuition says it's better to depend
on the external libraries and ignore the bundled ones.
I think I'll add a dependency on iconv, and move id3tag and mad in
an mp3 flavor, as I can see people not needing MP3 support.
> Missing system lib: c.37 (/usr/local/bin/mpd) > Missing system
lib: m.2 (/usr/local/bin/mpd) > Missing system lib: z.4
(/usr/local/bin/mpd) > Missing system lib: pthread.6 (/usr/local/bin/mpd)
These, I assume, would go in WANTLIB. As I understand it, WANTLIB
is for registering dependencies on libraries that are part of the
base system. I wonder why this was chosen over simply adding support
for this in LIB_DEPENDS. Anyway, this leads me to another question:
how to determine the version of a library to depend on? I should
think my port doesn't need the very latest version of the C library,
but how do I know which version is new enough?
-- Bob
