On Wed, Oct 31, 2007 at 09:21:54AM -0700, Doug Barton wrote: > On Wed, 31 Oct 2007, Peter Pentchev wrote: > >> Errr... maybe I should actually take a careful look at portmaster first, >> but after a cursory look at portmaster.sh.in... how do you handle the >> case of a port installation that executes commands from a runtime >> dependency? That is, a runtime dependency that is actually used at >> install time, too? > > That should be a build dependency then. I'll take a look at the example you > cited, but my gut feeling is that what you're describing shouldn't happen.
Erm, nope... A build dependency is not meant to modify anything on the user's system, but the installation process may need to, say, rebuild indexes or otherwise update some kind of configuration. Think add-on packages - some of them might need some kind of registration in the main package's configuration. At least that's the way I see it, and ICBW, but I think that there are various legitimate cases when a run-time dependency ought to be installed before the package installation itself. For more examples, take a look at the plist of most X11 fonts (@exec fc-cache), most JDK implementations (@exec registervm), most docbook-* ports (@exec xmlcatmgr), some GNOME ports like gnomevfs (@exec gconftool-2), and many others. G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I am the thought you are now thinking.
pgpeTCkSXF0M5.pgp
Description: PGP signature
