On Tue, 2007-12-04 at 08:50 -0600, Rex Dieter wrote: > Jesse Keating wrote: > > > On Tue, 04 Dec 2007 07:55:41 -0600 > > Rex Dieter <[EMAIL PROTECTED]> wrote: > > > >> Sigh, so can someone come up with a better solution to "I want to > >> install pkg foo, where it defines env vars, and pkgs consuming/using > >> pkg foo shouldn't need to know it's implementation details (ie, which > >> file in /etc/profile.d/ needs to source'd)" ? > > > > How do you plan to solve this when installing on a real system? User > > installs a bunch of -devel packages, tries to do an rpmbuild, fail. > > What then? > > The easiest (and only) solution I see so far is my initial suggestion: > "start a (new) login shell". > > If that's not acceptable, then we're stuck with the status-quo.
Why not convert qt to use pkg-config like so many other projects do, rather than stuffing build configuration details into my environment, where I don't care about them 99% of the time? -- Fedora-buildsys-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
