Manually registering dependencies for ports

Matthew Seaman m.seaman at
Mon Jun 7 07:54:05 UTC 2010

Hash: SHA1

On 07/06/2010 02:10:33, Stephen Montgomery-Smith wrote:
> Stephen Montgomery-Smith wrote:

> OK, after that appropriate chastising, let me try again.  This time I
> did test it.
> So, suppose you have a script xxx that uses port yyy.  So this will work:
> echo xxx >> /var/db/pkg/yyy/+REQUIRED_BY
> mkdir /var/db/pkg/xxx
> touch /var/db/pkg/xxx/+CONTENTS
> On the other hand, this will cause programs like pkg_info and
> pkg_version to get out of sorts.  And I guess if you use programs like
> port-upgrade (which I don't), who knows what damage this might cause.
> So --- this is what I would do.  If I had a set of scripts that I wanted
> to install, I would write my own local port whose job is to install the
> scripts, and which lists the needed dependencies as RUN_DEPENDS.

So, you're creating your own meta-port that exists only to be depended
on by the ports you specifically want to have installed?  That's a
really good idea.  You might need to fill out the contents of your
"wanted-ports" meta-port a bit more, but the concept seems sound to me.

It shouldn't cause horrendous problems with most package tools -- they
all cope with things like bsdpan- ports already, which don't have any
directory in the ports tree.  That means the standard ports management
tools (portupgrade, portmaster) won't be able to update them, but in
this case there's no need to do that.




- -- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP:     Ramsgate
JID: matthew at               Kent, CT11 9PW
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla -


More information about the freebsd-ports mailing list