Where should "contrib" scripts and utilities be installed?
Jeffrey Goldberg
jeffrey at goldmark.org
Wed Jun 11 23:29:12 UTC 2008
On Jun 10, 2008, at 10:24 AM, Peter Pentchev wrote:
> On Mon, Jun 09, 2008 at 08:54:49PM -0400, Sahil Tandon wrote:
>> The existence of ports with a "-contrib" suffix suggests you may
>> need to
>> create a distinct port for the contrib files. databases/postgresql-
>> contrib,
>> for example.
> Actually, that is not strictly necessary. There are other ports that
> do things in slightly different ways:
> - some things in contrib/ are merely documentation snippets that
> belong in share/doc/$PACKAGE, as Jeffery suggested
> - some things in contrib/ are sample additions, implementations,
> clients,
> add-ons and such that *might* belong in share/examples/$PACKAGE
> - some things in contrib/ are scripts, clients, add-ons and such that
> might also belong in libexec/$PACKAGE (if they are executable files)
> or share/$PACKAGE (if they are not... I can't think of any examples
> right now, but there might be)
> - some things in contrib/ are really best left in a separate port :)
I was hoping that I wouldn't have to think at all. Now it looks like
I will have to think about where each bit belongs. Oh, well.
> For rsnapshot itself - erm, I don't see a contrib/ directory in
> its source; do you mean the utils/ directory, or are you looking at
> some version that is not in the Ports Collection yet? :)
Sorry. Yes, I was thinking of the utils directory.
> If it is
> utils/ that you mean, then, well, it's actually your choice - the
> things
> there seem to be little scripts that may live in $EXAMPLESDIR, may
> live in libexec/rsnapshot/, and may live in a separate rsnapshot-utils
> port. Either way would be fine, at least IMHO.
OK. I'll just pick one and send the pr to the port maintainer who may
pick some other location.
Cheers,
-j
--
Jeffrey Goldberg http://www.goldmark.org/jeff/
More information about the freebsd-ports
mailing list