On Aug 4, 2008, at 03:58 , Alex Kloss wrote:
Hello all,
I've recently become an avid user of the Quod Libet music player, but
I'm disappointed that none of its plugins are in the ports tree.
I'd like to begin porting several of the plugins to FreeBSD, but I
have a few questions about the process:
The plugins are single-file Python scripts, which you simply drop into
/usr/local/share/quodlibet/plugins/ and then enable in Quod Libet. In
order to download them, you must pull them from Quod Libet's trunk in
Subversion. This doesn't sound like a good idea to me, because there's
no way to guarantee that a given plugin will remain stable all the
time. If I ported a plugin, is it advisable to pull the distfile from
trunk?
What about pulling a particular Subversion revision that is the way I
did it
I had a do-fetch target that fetched the subversion revision to a
subdirectory
in /usr/ports/distfiles then used tar to make a file-rev.tar.bz2.
Then just
carry on as normal. I do not want to clutter the list with this
Makefile
I could send to directly if you think it might help.
Also: is it a better idea to separate all of the plugins into
individual ports, or create a few ports that each install a particular
category of plugins? There's over 20 plugins, so I'm not sure if the
ports team would appreciate me trying to clutter up their tree
You could use the OPTIONS to make a list of all the plugins
and set the most popular ones as yes, then make config
will allow you to make a selection.
e.g audio/sox has 12 options.
Thanks in advance!
Alex Kloss
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-
[EMAIL PROTECTED]"
Best regards,
Christopher Hall christopherhall.hswATgmail.com
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
