Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master grimoire by Arjan Bouter (63d4188c17032e168901f4a32cccee9ef733635c)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: Arjan Bouter <abouter AT gmail.com>
  • To: sm-commit AT lists.ibiblio.org
  • Subject: Re: [SM-Commit] GIT changes to master grimoire by Arjan Bouter (63d4188c17032e168901f4a32cccee9ef733635c)
  • Date: Wed, 17 Sep 2008 22:09:23 +0200

On Wed, 17 Sep 2008 15:52:33 -0400
flux <flux AT sourcemage.org> wrote:

> Jaka Kranjc (smgl AT lynxlynx.info) wrote [08.09.17 15:39]:
> > On Wednesday 17 of September 2008 21:35:59 Arjan Bouter wrote:
> > > > And xorg-server doesn't autodetect an installed printproto?
> > >
> > > sure it will, that's exactly why it had to be removed from the list of
> > > depends. as it is now, IF the user selects libxp as an optional_depends
> > > for
> > > which there is a configure option ONLY THEN should printproto be pulled
> > > in.
> > > Which it does because libxp depends on it.
> > >
> > > If depends printproto is in there, then the build will fail if libxp is
> > > disabled as optional_depends.
> > >
> > > What I'm trying to say is that the current situation (libxp pulling in
> > > printproto ONLY when needed) is probably the only sane way to make
> > > libxp+printproto optional.
> > >
> > > Feel free to prove me wrong though :)
> > I'm just saying there seems to be a problem.
> >
> > 0. nothing installed
> > 1. cast xorg-server, enable libxp, printproto is also cast
> > 2. dispel libxp, recast xorg-server and say no to libxp
> > will this step work or not, since printproto is still installed?
> >
> > --
> > We cannot command nature except by obeying her. --Sir Francis Bacon
> > Have a sourcerous day! www.sourcemage.org
>
> Could this just be fixed with a trigger for removal of printproto on
> dispelling libxp?
>

That won't work. Just like with linux-pam. If you cast linux-pam and enable
the optional_depends on it in other spells, you'll have to recast every spell
once you remove linux-pam.

If you build X with libxp+printproto and wish to remove it later, then you'll
need to remove both libxp+printproto and recast most of X.

It's not that different from other dependency chains really. scenario 2 will
fail for most dependency chains because of leftover spells (aliens) still
being
installed.

Ruskie mentioned this as well and we're looking into it.

Arjan

+=======
Source Mage GNU/Linux developer,
http://www.sourcemage.org
Registered as user #310617 with the Linux Counter,
http://counter.li.org.
GnuPG Key 79D4B14E = 94AD 3FD1 E259 67ED 632E 2B06 CFBE 1154 79D4 B14E
+===





Archive powered by MHonArc 2.6.24.

Top of Page