-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| Ferris McCormick wrote:
| | is a timesaver. I don't know if this works generally, but I have never
| | had any trouble making libGL in parallel when building it by hand.
|
| Alright, I've switched to emake and we'll see how i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
| is a timesaver. I don't know if this works generally, but I have never
| had any trouble making libGL in parallel when building it by hand.
Alright, I've switched to emake and we'll see how it goes.
Donnie
-BEGIN PGP S
On Thu, 2005-08-11 at 23:29 +, Ferris McCormick wrote:
>
> On Thu, 11 Aug 2005, Donnie Berkholz wrote:
>
> > --[PinePGP]--[begin]--
> > Ferris McCormick wrote:
> > > I'm happy with libGL; I just reverted the ebuild to be as it started,
> >
maillog: 11/08/2005-21:06:34(-0700): Donnie Berkholz types
> Georgi Georgiev wrote:
> | As you can see, it's the "static" in the end of the line. Maybe you
> | should grep for "-static" instead.
>
> | - To avoid eventual problems with similarly named libraries (libpam and
> | libpam_misc for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
| As you can see, it's the "static" in the end of the line. Maybe you
| should grep for "-static" instead.
| - To avoid eventual problems with similarly named libraries (libpam and
| libpam_misc for example; grepping for
maillog: 11/08/2005-16:05:02(-0700): Donnie Berkholz types
> Donnie Berkholz wrote:
> > Attached an update to incorporate this and your other grep comments.
>
> Here's a new one. It prints some useful information while it's
> searching, like OK or Not found!. Also fixes a little more ugly output
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
> Attached an update to incorporate this and your other grep comments.
Here's a new one. It prints some useful information while it's
searching, like OK or Not found!. Also fixes a little more ugly output
(double/single quotes a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 11 Aug 2005, Donnie Berkholz wrote:
--[PinePGP]--[begin]--
Ferris McCormick wrote:
I'm happy with libGL; I just reverted the ebuild to be as it started,
but to define a sparc-specific set of d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
> I'm happy with libGL; I just reverted the ebuild to be as it started,
> but to define a sparc-specific set of dri drivers. All my problems came
> from my mistaken belief that mesa would still build cleanly using the
> sparc as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
> Why not pull these greps out of the loop? No need to do the *same* thing
> for every library. Or did you forget to mention $libname in there?
My rationale was that over the course of a compilation, both shared and
static libs
maillog: 11/08/2005-11:58:31(-0700): Donnie Berkholz types
> Donnie Berkholz wrote:
> > Here's a slightly better version:
>
> And here's the enhanced, scripted version. It traces libs back to their
> packages to really make things easy.
>
> Seems to work quite well.
>
> Thanks,
> Donnie
> echo
On Thu, 2005-08-11 at 12:25 -0700, Donnie Berkholz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ferris McCormick wrote:
> > Notice, however, that the mesa ebuild does not seem to install the dri
> > drivers anyplace. I suppose they should go
> > into /usr/lib/xorg/modules/drivers,
maillog: 11/08/2005-21:11:35(+0200): Jan Spitalnik types
> Dne čt 11. srpna 2005 20:58 Donnie Berkholz napsal(a):
> > Donnie Berkholz wrote:
> > > Here's a slightly better version:
> >
> > And here's the enhanced, scripted version. It traces libs back to their
> > packages to really make things eas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Spitalnik wrote:
> as it should be equivalent.
You'd think so, but consider this case:
Package A provides foo.so
Package B provides foo.a
Package C links against both
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
> Notice, however, that the mesa ebuild does not seem to install the dri
> drivers anyplace. I suppose they should go
> into /usr/lib/xorg/modules/drivers, but the don't. It seems that the
> ebuild uses mesa's 'installmesa' sc
Dne čt 11. srpna 2005 20:58 Donnie Berkholz napsal(a):
> Donnie Berkholz wrote:
> > Here's a slightly better version:
>
> And here's the enhanced, scripted version. It traces libs back to their
> packages to really make things easy.
you can replace (starting line 37)
if $(grep ' \-l[a-zA-Z
On Thu, 2005-08-11 at 11:02 -0700, Donnie Berkholz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Donnie Berkholz wrote:
> > And why is this a good thing? I'm adamantly against building the non-glx
> > libGL here for standard use, and I will continue to oppose it. Be normal
> > peopl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
> Here's a slightly better version:
And here's the enhanced, scripted version. It traces libs back to their
packages to really make things easy.
Seems to work quite well.
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
> And why is this a good thing? I'm adamantly against building the non-glx
> libGL here for standard use, and I will continue to oppose it. Be normal
> people and do the same thing as everybody else in the world who's ever
> used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
> 3. With USE=-dri, for testing purposes (and in the end, perhaps for
> performance reasons as well), it seems better to change the make target
> to HOSTCONF=linux-sparc, and let user's CFLAGS define the architecture.
> When yo
On Wed, 2005-08-10 at 17:46 -0700, Donnie Berkholz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ferris McCormick wrote:
> | It always makes sense to enable glx (Mesa) whether there is DRI support
> | or not; some applications can run adequately well using the
> | Mesa-indirect appr
On Wed, 2005-08-10 at 17:46 -0700, Donnie Berkholz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ferris McCormick wrote:
> | It always makes sense to enable glx (Mesa) whether there is DRI support
> | or not; some applications can run adequately well using the
> | Mesa-indirect appr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| A few updates:
|
| I'm working on a Mesa ebuild to add; this will provide the gl.h
| everyone's been complaining about missing. My dev box is really screwy
| because of orphaned files, things lying around from CVS, etc, so I
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| Per-Erik Westerberg wrote:
| | Ubuntu "Breezy" has also problems with the "fixed" font when I updated
| | it, the "fonts.alias" file is missing from the "/usr/share/fonts/misc"
| | directory, maybe it is the same problem that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
| maillog: 10/08/2005-23:01:30(-0700): Donnie Berkholz types
|>Needing to set ModulePath at all in a standard installation is broken.
|>This shouldn't need to be in a configuration file; none of the tools I'm
|>aware of generate
maillog: 10/08/2005-23:01:30(-0700): Donnie Berkholz types
> Georgi Georgiev wrote:
> | Hm, why not just forget the transition, stick a warning telling people
> | to add
> |
> | ModulesPath "/usr/lib/modules"
> | ModulesPath "/usr/lib/xorg/modules"
>
> Needing to set ModulePath at all in a standar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 11 Aug 2005, Ferris McCormick wrote:
| With mach64, the problem on sparc has been the hardware itself, if I
| remember correctly. That is, kernel, xorg are fine, but the mach64
| card
| used on U5/U10 is memory-deficient. Someone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
| Hm, why not just forget the transition, stick a warning telling people
| to add
|
| ModulesPath "/usr/lib/modules"
| ModulesPath "/usr/lib/xorg/modules"
Needing to set ModulePath at all in a standard installation is broken.
T
maillog: 10/08/2005-22:08:36(-0700): Donnie Berkholz types
> Georgi Georgiev wrote:
> | What about new revisions of the monolithic xorg that will install in
> | /usr/lib/xorg/modules followed by new revisions of all packages like
> | opengl-update, nvidia, ati-whatever, that will depend on the newe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
| What about new revisions of the monolithic xorg that will install in
| /usr/lib/xorg/modules followed by new revisions of all packages like
| opengl-update, nvidia, ati-whatever, that will depend on the newer xorg
| release?
maillog: 10/08/2005-21:45:58(-0700): Donnie Berkholz types
> Donnie Berkholz wrote:
> > Georgi Georgiev wrote:
> >
> >>>It seems that the current xorg-server installs all modules in
> >>>/usr/lib/xorg/modules. Any idea why? It used to be /usr/lib/modules
> >>>until recently, and that's still where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
> Georgi Georgiev wrote:
>
>>>It seems that the current xorg-server installs all modules in
>>>/usr/lib/xorg/modules. Any idea why? It used to be /usr/lib/modules
>>>until recently, and that's still where opengl-update symlinks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
> It seems that the current xorg-server installs all modules in
> /usr/lib/xorg/modules. Any idea why? It used to be /usr/lib/modules
> until recently, and that's still where opengl-update symlinks stuff to,
> and also where vnc
maillog: 09/08/2005-11:16:52(-0700): Donnie Berkholz types
> Donnie Berkholz wrote:
> | If you find bugs that aren't purely ebuild problems, do not file them at
> | bugs.gentoo.org -- go to bugs.freedesktop.org, in the xorg product.
> |
> | Two USE flags you will care about are "dri" and "glx" -- b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
| It always makes sense to enable glx (Mesa) whether there is DRI support
| or not; some applications can run adequately well using the
| Mesa-indirect approach, and some graphics cards --- e.g., Elite == afb
| --- don't allow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 10 Aug 2005, Donnie Berkholz wrote:
--[PinePGP]--[begin]--
Ferris McCormick wrote:
| I wrote the note very fast, and it was not too clear. With sunffb, the
| kernel code for current 2.6.x (x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
| I wrote the note very fast, and it was not too clear. With sunffb, the
| kernel code for current 2.6.x (x > 6) is broken, and davem has taken dri
| support out of the xorg sunffb driver (to paraphrase him, you can't do
| bot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 10 Aug 2005, Donnie Berkholz wrote:
--[PinePGP]--[begin]--
Ferris McCormick wrote:
| > Done. It's not quite right, yet, but it can now be worked with. For
| > sparc, we do not want a lot of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| Ferris McCormick wrote:
| |> Done. It's not quite right, yet, but it can now be worked with. For
| |> sparc, we do not want a lot of ..._dri.so modules (even though that is
| |> the target being used) because the kernel does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
|> Done. It's not quite right, yet, but it can now be worked with. For
|> sparc, we do not want a lot of ..._dri.so modules (even though that is
|> the target being used) because the kernel does not support them. So,
|> curr
On Wed, 2005-08-10 at 10:53 -0700, Donnie Berkholz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ferris McCormick wrote:
> | 2. But to get sparc assembler built correctly, the following patch
> | seems correct:
>
> Looks good to me.
>
> |
>
> Just go ahead and commit it.
Done.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Per-Erik Westerberg wrote:
| Ubuntu "Breezy" has also problems with the "fixed" font when I updated
| it, the "fonts.alias" file is missing from the "/usr/share/fonts/misc"
| directory, maybe it is the same problem that people are experiencing?
I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
| 2. But to get sparc assembler built correctly, the following patch
| seems correct:
Looks good to me.
| (Alternative is to create a complete linux-dri-sparc config file; I can
| do that if you like.)
No need if you don't
Ubuntu "Breezy" has also problems with the "fixed" font when I updated
it, the "fonts.alias" file is missing from the "/usr/share/fonts/misc"
directory, maybe it is the same problem that people are experiencing?
/ Per-Erik
tis 2005-08-09 klockan 11:16 -0700 skrev Donnie Berkholz:
> Donnie Berkh
On Wed, 2005-08-10 at 12:46 +, Ferris McCormick wrote:
> On Tue, 2005-08-09 at 19:40 -0700, Donnie Berkholz wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
>
> > Good catch. I was going to get to the rest of the GL headers after
> > getting Mesa working.
>
> Another comment
On Tue, 2005-08-09 at 19:40 -0700, Donnie Berkholz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Good catch. I was going to get to the rest of the GL headers after
> getting Mesa working.
Another comment about Mesa. Mesa, as distributed, has "built in"
architectures it can build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| A few updates:
|
| I'm working on a Mesa ebuild to add; this will provide the gl.h
| everyone's been complaining about missing. My dev box is really screwy
| because of orphaned files, things lying around from CVS, etc, so I
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| Ciaran McCreesh wrote:
| | Hrm. Is this going to be sanely doable by your average dev? How long
| | a dep string would we be having in typical cases? How about in bad
| | cases?
|
| It shouldn't be difficult in most cases,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
| Furthermore, make sure you don't install the headers in /usr/include/GL,
| but in a location that opengl-update would know how to handle.
Good catch. I was going to get to the rest of the GL headers after
getting Mesa working
maillog: 09/08/2005-11:16:52(-0700): Donnie Berkholz types
>
> Also there have been errors of the freetype/type1/trap modules not found
> on startx. They aren't yet built in xorg-server, so you may need to copy
> them over from an older install.
Add to that the "bitmap" and "pcidata" modules -- th
maillog: 09/08/2005-11:16:52(-0700): Donnie Berkholz types
> Donnie Berkholz wrote:
> | If you find bugs that aren't purely ebuild problems, do not file them at
> | bugs.gentoo.org -- go to bugs.freedesktop.org, in the xorg product.
> |
> | Two USE flags you will care about are "dri" and "glx" -- b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| If you find bugs that aren't purely ebuild problems, do not file them at
| bugs.gentoo.org -- go to bugs.freedesktop.org, in the xorg product.
|
| Two USE flags you will care about are "dri" and "glx" -- both are
| necessary t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Caleb Tennis wrote:
| On Monday 08 August 2005 08:14 pm, Donnie Berkholz wrote:
|
|>If you could bring up some specific examples, we could discuss them.
|
|
| Sure. Qt has optional support for xkb, tablet, fontconfig, xrender,
xrandr,
| xcursor, xine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
| emerging libXfont with font-server made xorg-server link just fine.
|
| Still, I believe that it is xorg-server that has to be fixed. It needs
| to get "NOFONTSERVERACCESS" defined, which will avoid the call to
| fs_register_f
On Tuesday 09 August 2005 15:03, Caleb Tennis wrote:
> Let me follow up with that I'm all for adding the use flags IF other
> packages would make use of them as well. I just really hate adding 8 local
> use flags for this pretty heavily used package that won't add much utility
> to anything else a
> Yep, you're a heretic. :)
> How would you propose that DEPEND information make it's way up the
> portage stack, and ultimately affects the depgraph?
>
> What you're suggesting is effectively "suggested" deps, which are a
> bit backwards considering we have "optional" deps, the 8 flags you
> disli
On Tue, Aug 09, 2005 at 07:36:31AM -0500, Caleb Tennis wrote:
> On Monday 08 August 2005 08:14 pm, Donnie Berkholz wrote:
> > If you could bring up some specific examples, we could discuss them.
>
> Sure. Qt has optional support for xkb, tablet, fontconfig, xrender, xrandr,
> xcursor, xinerama (
On Monday 08 August 2005 08:14 pm, Donnie Berkholz wrote:
> If you could bring up some specific examples, we could discuss them.
Sure. Qt has optional support for xkb, tablet, fontconfig, xrender, xrandr,
xcursor, xinerama (already a use flag), xshape, and xsm.
I'd really hate to add 8 more use
maillog: 08/08/2005-01:08:03(-0700): Donnie Berkholz types
>> snip
> The font-server flag may be necessary in libXfont, but I haven't fully
> explored this yet. If it turns out to be the case, it'll be removed as
> an optional flag and forced on.
Unfortunately, it seems it does. I did it with "-fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Caleb Tennis wrote:
| What is the plan for packages (I'm thinking other x11-libs/ packages and
| window managers) which can optionally depend on various X11 libraries?
Do we
| need use flags for "xcursor", "xrender","xsm" and the like to pull in the
On Monday 01 August 2005 03:54 pm, Donnie Berkholz wrote:
> I eagerly await your questions and concerns.
Donnie,
What is the plan for packages (I'm thinking other x11-libs/ packages and
window managers) which can optionally depend on various X11 libraries? Do we
need use flags for "xcursor", "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
| Donnie,
| Unless you a good reason for me not to do so, I am going to start
| adding the ~sparc keyword to the Modular X ebuilds and then start
| playing with them locally. (I'm not going to mess with your global
| package
Donnie,
Unless you a good reason for me not to do so, I am going to start
adding the ~sparc keyword to the Modular X ebuilds and then start
playing with them locally. (I'm not going to mess with your global
package masks, of course, but I do want to work with a real ~sparc
keyword rather than fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| What I meant by "tomorrow" was "next week," of course. =) I just made
| the first commits.
Most things are committed, with the exception of the metabuilds. I'm
still working on them.
If you want to try it, you'll have to add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| As I said, very soon. It's out. I will begin adding new categories as
| necessary and the beginnings of the modular tree tomorrow.
What I meant by "tomorrow" was "next week," of course. =) I just made
the first commits.
Plea
that's great :)
Thanks for doing that.
That's exactly what I done with XCB ebuilds. Maybe some of you don't
know xcb, it a remplacement for Xlib. Currently it only available on
cvs. I think it couldn't have to be ignore it.
Some ebuilds for :
http://guybrush.ath.cx/svn/public/portage/x11-libs/
W
On Wednesday 03 August 2005 07:41, Donnie Berkholz wrote:
> If you want your patch back in, you will _need_ to file it upstream and
> have it committed before we will re-add it.
While I generally agree with this "the closer to upstream, the better", I hope
that this can be a bit more easy for comp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As a further note on this:
We will be dropping all patches that are not upstream and are not
obviously Gentoo-specific configuration changes.
If you want your patch back in, you will _need_ to file it upstream and
have it committed before we will re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Maitin-Shepard wrote:
| If I understand correctly, all of the packages in x11-proto will only
| install header files. Are these header files ever useful on their own
| though? Would it make more sense to include the header files
| in various
If I understand correctly, all of the packages in x11-proto will only
install header files. Are these header files ever useful on their own
though? Would it make more sense to include the header files
in various library packages?
--
Jeremy Maitin-Shepard
--
gentoo-dev@gentoo.org mailing list
On Mon, Aug 01, 2005 at 02:23:06PM -0700, Donnie Berkholz wrote:
> Your suggestion of adding a few new virtuals is a good idea, but I think
> the metabuilds for libraries, drivers, etc. can substitute for it. It's
> not clear to me that there are many common configurations that could be
> dealt wit
Donnie Berkholz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| The new categories are x11-apps, x11-proto and x11-drivers. Of these,
| the name for x11-proto (the protocol headers) is debatable. The upstream
| module they're all in is called "proto," and their pkg-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| The new categories are x11-apps, x11-proto and x11-drivers. Of these,
| the name for x11-proto (the protocol headers) is debatable. The upstream
| module they're all in is called "proto," and their pkg-config (*.pc)
| files ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Mon, 01 Aug 2005 19:23:37 -0400 Alec Warner <[EMAIL PROTECTED]>
> wrote:
> | > Hrm. Is this going to be sanely doable by your average dev? How
> | > long a dep string would we be having in typical cases? How about in
> |
On Mon, 01 Aug 2005 19:23:37 -0400 Alec Warner <[EMAIL PROTECTED]>
wrote:
| > Hrm. Is this going to be sanely doable by your average dev? How
| > long a dep string would we be having in typical cases? How about in
| > bad cases?
| >
| The more formal the depstring, the quicker the packages b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Mon, 01 Aug 2005 14:54:04 -0700 Donnie Berkholz
> <[EMAIL PROTECTED]> wrote:
> | Ciaran McCreesh wrote:
> | | Well... What I was mainly thinking (and assuming we don't have the
> | | new virtuals system by whenever this beco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| On Mon, 01 Aug 2005 14:54:04 -0700 Donnie Berkholz
| <[EMAIL PROTECTED]> wrote:
| | Ciaran McCreesh wrote:
| | But see, that's the thing; no packages should just generally say "Give
| | me the X libraries" other than temporari
On Mon, 01 Aug 2005 14:54:04 -0700 Donnie Berkholz
<[EMAIL PROTECTED]> wrote:
| Ciaran McCreesh wrote:
| | Well... What I was mainly thinking (and assuming we don't have the
| | new virtuals system by whenever this becomes relevant) is that a
| | metapackage could represent, say, "the core x11 libr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| Well... What I was mainly thinking (and assuming we don't have the new
| virtuals system by whenever this becomes relevant) is that a metapackage
| could represent, say, "the core x11 libraries as provided by xorg". This
| is
On Mon, 01 Aug 2005 14:23:06 -0700 Donnie Berkholz
<[EMAIL PROTECTED]> wrote:
| Your suggestion of adding a few new virtuals is a good idea, but I
| think the metabuilds for libraries, drivers, etc. can substitute for
| it. It's not clear to me that there are many common configurations
| that could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| On Mon, 01 Aug 2005 13:54:27 -0700 Donnie Berkholz
| <[EMAIL PROTECTED]> wrote:
| | Until such time as that becomes possible for everyone to do, the
| | x11-libs metabuild will PROVIDE virtual/x11. But realize that not
| | eve
On Mon, 01 Aug 2005 13:54:27 -0700 Donnie Berkholz
<[EMAIL PROTECTED]> wrote:
| Until such time as that becomes possible for everyone to do, the
| x11-libs metabuild will PROVIDE virtual/x11. But realize that not
| everybody will have or want all the X libraries installed, when they
| only need a f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(This is an expanded, updated version of a recent blog post, so some of
you may have already seen parts of it.)
Background: Upstream is splitting up the monolithic X.Org X11 release
into a huge number of modular releases, the combination of which wil
83 matches
Mail list logo
