Date: Sun, 06 Jun 2010 19:16:27 -0500 From: Stephen Montgomery-Smith <stephen@missouri.edu> To: Thomas Rasmussen <thomas@gibfest.dk> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: Manually registering dependencies for ports Message-ID: <4C0C3A5B.8010707@missouri.edu> In-Reply-To: <4C0C34FC.4030603@gibfest.dk> References: <4C0C34FC.4030603@gibfest.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Rasmussen wrote: > Hello, > > I've been wondering about something: When I write a script or webapp that > needs some port to run, like a perl module, I install the needed port and > life is good (tm). A year later when I've completely forgotten about the > script I go do some spring-cleaning of the ports on the server, and I see > some perl module that doesn't have any dependencies, and delete it. Fast > forward a few days when I discover the script doesn't work anymore, cue > face-palm, remove bullet from foot, etc. > > Is there some way I can register a dependency to prevent this ? Like > adding a flag to an installed port to say "something outside of the ports > system depends on this" along with a user specified comment string. When you install a script - let's call it xxx - that depends upon port yyy, you could do something like echo xxx >> /var/db/pkg/yyy/+REQUIRED_BY I think this would work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C0C3A5B.8010707>