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 21:35:59 +0200

On Wed, 17 Sep 2008 20:24:16 +0200
Jaka Kranjc <smgl AT lynxlynx.info> wrote:

> On Wednesday 17 of September 2008 20:19:21 Arjan Bouter wrote:
> > On Wed, 17 Sep 2008 18:13:02 +0200
> >
> > Jaka Kranjc <smgl AT lynxlynx.info> wrote:
> > > On Wednesday 17 of September 2008 00:00:26 Arjan Bouter wrote:
> > > > > > -depends printproto
> > > > >
> > > > > Is this intentional?
> > > > >
> > > > > --
> > > > > Ladislav Hagara
> > > >
> > > > Yes it is, libxp depends on printproto so it will be pulled in if
> > > > printing is enabled. But having printproto installed makes xorg-server
> > > > fail when disabling libxp.
> > >
> > > But if someone decide to not want xorg-server with libxp anymore, they
> > > won't be able to build it at all!?
> > >
> > > --
> > > We cannot command nature except by obeying her. --Sir Francis Bacon
> > > Have a sourcerous day! www.sourcemage.org
> >
> > Sure they can. libxp depends on printproto, so if libxp is enabled as
> > optional_depends for xorg-server it'll pull in printproto. On the other
> > hand, if xorg-server depends on printproto, it'll need libxp and
> > everything
> > X related HAS to be built with libxp.
> >
> > This way the SA can make a choice instead being forced to use libxp &
> > printproto like we used to do.
> And xorg-server doesn't autodetect an installed printproto?
>
> LP
> --
> We cannot command nature except by obeying her. --Sir Francis Bacon
> Have a sourcerous day! www.sourcemage.org

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 :)


Arjan Bouter

+=======
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