-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
> FRITZCAPI_CARDS FCDSL_CARDS VIDEO_CARDS INPUT_DEVICES LINGUAS
>
> Do any of these not follow the same pattern of empty var == all installed?
> Any
> objections to making that a requirement for adding a new USE_EXPAND variable?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
> The 6.8.99 snapshot ebuilds
> (hard masked for testing) are the CVS development snapshots of this in
> portage, still unsplit, as it hasn't yet been split upstream, AFAIK.
The splitting is underway. Most of the protocol headers and lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
> Any reason why INPUT_DEVICES is needed in USE_EXPAND rather than just as
> local
> USE flags? It's kind of the odd one out among the above.
The reasoning for that is that hardware support doesn't make sense as
USE flags, so it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Warner wrote:
> Donnie Berkholz wrote:
> The reasoning for that is that hardware support doesn't make sense as
> USE flags, so it should be something else. In this case, that was
> INPUT_DEVICES. We haven't been able to tak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been wondering lately with the discussion of yet more new
categories, why don't we do repocopies to move packages? Note that I'm
talking about packages switching categories and explicitly _not_ about
package name changes.
Although this would requ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Caleb Tennis wrote:
> DEPEND="$(qt_min_version 3.0)"
> or
> DEPEND="qt? ( $(qt_min_version 3.1.2-r2) )"
>
> And the eclass will expand out all Qt3 ebuilds which satisfy the statement.
I'm no expert on portage, but running random functions in DEPEND
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aron Griffis wrote:
> Robin H. Johnson wrote:[Sat Jul 02 2005, 02:47:48PM EDT]
>
>>After such a move of directories, CVS clients running their next update
>>would find NO record of the old directory when they attempted to update
>>it, and the CVS clie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
twofourtysix wrote:
> On 05/07/05, Jon Portnoy <[EMAIL PROTECTED]> wrote:
>
>>On Tue, Jul 05, 2005 at 06:59:24AM +0100, twofourtysix wrote:
>>
>>>uncensored, I'll accept that Gentoo as an organisation has no
>>>influence over the content. Otherwise, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
> personally i'd support a doxinetd func that would check to see if xinetd is
> installed rather than go with a USE flag ...
This kind of auto-enabling stuff is our bane upstream, so I don't see
that creating more of it ourselve
On Thu, 2005-07-07 at 08:19 -0400, Ned Ludd wrote:
> I would be in favor of EAPI= or an even shorter variable name.
>
> strlen(EBUILD_FORMAT) * 19546 = 249K
> strlen(EAPI) * 19546 = 77K
> strlen(EV) * 19546 = 39K
>
> Where 19546 is the number if ebuilds in the tree as.
So, the size of the tree
On Thu, 2005-07-07 at 20:28 +0200, Maurice van der Pot wrote:
> On Thu, Jul 07, 2005 at 10:52:06AM -0700, Donnie Berkholz intended to write:
> > size for the options above 0.05%, 0.02% and 0.01% respectively. In
> > any case, nearly irrelevant to its present size.
Mixed up my dec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kristian Benoit wrote:
> I'm trying to add a new command to ebuild (preconfig) for packages like
> busybox that has to be configured prior to compile and that would be a
> cannot really use USE as it probably have undreads of USE that does not
> yet ex
On Fri, 2005-07-15 at 18:56 -0700, Michael Marineau wrote:
> I just ment that by providing profile.d (and similar things) would let
> users customize
> their profile without having to edit a gentoo installed file, making
> upgrades a bit
> easier. To prevent abuse perhaps portage could enforce a b
On Sat, 2005-07-16 at 22:48 -0400, Mike Frysinger wrote:
> x11-base/xorg-x11 (no idea what it's trying to do with /etc/profile.d/xprint*)
Don't know, don't care, don't use xprint. Pull it from your USE flags
and all will be well. =)
I don't actively maintain xorg's xprint support; that's largely
On Sun, 2005-07-17 at 22:07 -0700, Anthony Gorecki wrote:
> On Sunday, July 17, 2005 9:26 pm, Casey Allen Shobe wrote:
> > I'm also a bit confused about the portdir_overlay thing - If there
> > exists a -r15, do I then add a -r16 to make emerge realize an
> > update is available. What happens then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
| can we get you to actively remove the file then ? or move it into the
docs
| dir as like an example file, xprint.profile.d
OK, all the ebuilds are putting them as docs now. If anyone actually
uses xprint and it breaks, let me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
| On Monday 18 July 2005 07:47 pm, Donnie Berkholz wrote:
|
|>Mike Frysinger wrote:
|>| can we get you to actively remove the file then ? or move it into the
|>
|>docs
|>
|>| dir as like an example file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
| The AT guidelines (available for amd64 ATs here:
| http://www.gentoo.org/proj/en/base/amd64/tests/index.xml ) specifically
| mention testing "every conceivable permutation",
That's an absolute joke for reasonably large packages with s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Joseph Warner wrote:
| solution is done now, in the changelog, to be viewed by users. Metadata
| ideas were not liked because metadata is not versioned and the parsing
| would not be easy.
The metadata dtd explicitly supports versioning. It loo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
| The reason behind this is that at approximately two thirds of bugs
received
| are feature requests and they are drowning at the real bugs. More
importantly,
| the critical bugs are becoming very hard to keep track of. This, at a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian D. Harring wrote:
| Essentially it's squashing old noise on the bugs till we can actually
| address it. Like I said above, two main thrusts of work are stable,
| and mangling the codebase so that we can actually pull this stuff off,
| and with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Lohrke wrote:
| On Friday 29 July 2005 17:40, Diego 'Flameeyes' Pettenò wrote:
|
|>This can be read as "it's good to use epatch" ? :P
|
|
| It's just less text to write PATCHES="foo ...", if you don't have a
src_unpack
| function in the partic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Lohrke wrote:
| On Friday 29 July 2005 18:39, Donnie Berkholz wrote:
|
|>That doesn't really make any sense. You could just as easily use PATCHES
|>if you ran s/patch -p0
-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
-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 th
-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
-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 libra
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Martin wrote:
| Hi list,
|
| Bug 97447 wants a logrotate USE flag, which is used by about five
| packages locally. Unless there are any objections, I'll globalify it
| later today.
I think this flag is a bad idea. Why should I have to recompile a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| Files in /etc are expensive in terms of sysadmin time. The only things
| in /etc should be things that are both necessary and likely to be
| modified by a sysadmin.
So we should stop installing example files, too?
-BEGIN
-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
-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
Chris Gianelloni wrote:
| eg. If I want to change the subnet mask or default router on 50 machines
| on my network, I should be able to do so via a simple interface and have
| the work done automatically.
That's why we added c3 and clusterssh to the
-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 ju
-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
-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
-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
-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
-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,
| xcur
-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"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Huddleston wrote:
| I've been pretty busy this summer and haven't had much time to devote to
| the gcc-config changes we discussed here a couple months back until
| yesterday. I created a cvs repository for the development in
| gentoo/src/tool
-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
-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
-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,
-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
-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:
|> 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
-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) beca
-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
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
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
-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
-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?
-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
-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&#
-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"
| | dire
-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,
-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
-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 wo
-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
-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
-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
I started a brief migrating to modular X howto, on popular demand.
Comments and additions would be appreciated.
It's at
http://dev.gentoo.org/~spyderous/xorg-x11/migrating_to_modular_x_howto.txt
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: G
-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
-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
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/
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| I started a brief migrating to modular X howto, on popular demand.
| Comments and additions would be appreciated.
|
| It's at
| http://dev.gentoo.org/~spyderous/xorg-x11/migrating_to_modular_x_howto.txt
I just updated
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Skeggs wrote:
| I've attached a small test case which demonstrates a problem with event
| selection.
| I haven't had time yet to try this with XCreateWindow also, but I
| imagine I'll see
| similar results if I try to select for events on the wind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's another script I wrote, similar to the one for finding packages
that your package links with. But this one finds (tries to find)
X-headers that your package includes.
I didn't post to the modular X thread because it's really getting out of
con
-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&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Skeggs wrote:
|> Done, is there any more information I need to add to the report?
X log and X config are the usual suspects.
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC/YrqXVaO67S1rtsRAt6ZAKDn/IqjhMVW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I started a brief porting to modular X howto, to help devs get their
packages working properly with modular X.
It's at
http://dev.gentoo.org/~spyderous/xorg-x11/porting_to_modular_x_howto.txt
If there's anything I can add to help you out, just let m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Skeggs wrote:
| Try out the latest -r2 xorg-server first, which updates to CVS as of
| yesterday.
|
|
|> Still broken here.
I just added xorg-server-0.99.1-x86_64-1.patch, which fixes a
configure.ac use of amd64 to x86_64. Give it another shot in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corey Shields wrote:
| Archive links for the complete morning and afternoon sessions are at
| http://devconference.gentoo.org
Thanks Corey! I was unable to sit around all day Friday watching them,
so this will be really helpful.
Donnie
-BEGIN PG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
| What do I RDEPEND on if the app is statically linked, but requires a
| local X server to connect to, like many binary games require?
xorg-server is the package providing the servers. Alternately, there's
kdrive in the tree n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| Chris Gianelloni wrote:
| | What do I RDEPEND on if the app is statically linked, but requires a
| | local X server to connect to, like many binary games require?
|
| xorg-server is the package providing the servers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
| I was referring to games that require a local X server, which is pretty
| much all of the binary games, especially OpenGL-based ones. For
| anything non-OpenGL or source-based, the dependencies would be explicit
| on the lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Huddleston wrote:
| The eselect developers want to keep all eselect modules in their svn
| repository and distributed through a single package (app-admin/eselect).
| Their main reasons for this are better QA and less overhead for releases
| and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
| I don't quite get you here. GLEP 31 has been approved, no? That would
make
| it seem to me that the above suggestion is just making the QA tool help
| enforce existing policy. If there's a flaw in that line of thinking,
please
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Harring wrote:
| Kind of curious about people's opinion on the IUSE default use flag
| thing, initial syntax was (using the above example)
| IUSE="+client server"
| with client defaulting to on unless the user's config disables it-
| note, stric
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Harring wrote:
| Yeah, but the angle I'm pushing for default IUSE's ...er.. use is
| eliminating no* flags, and giving ebuild maintainers more flexibility
| in breaking the package down into conditionals.
|
| I really don't see -* being all that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| Ok. You have until whenever I next encounter Jeff to come up with a
| better name, or REVIEWED it is. And it seems I was dreaming about
| bugzilla allowing () stuff after keywords entries (maybe I was thinking
| of one of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| Nope, because I'm not marking things as "I will include this".
According to Bugzilla, it means more like: Contains content that should
be reviewed for integration. Patches, apps/scripts, etc...
which could be used as content
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| On Sat, 20 Aug 2005 15:06:34 -0600 R Hill <[EMAIL PROTECTED]>
| wrote:
| | Ciaran McCreesh wrote:
| | > I've been going through the EBUILD list at random and providing
| | > lists of things that need to be fixed before the ebu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan L. Adams wrote:
| What I see with Gentoo is this 'cathedral' being built where only those
| folks who have been 'approved' or 'blessed' as being l33t enough are
| allowed to review the code and actually cause a positive change when
| some bug i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan L. Adams wrote:
| What are the most common ebuild mistakes?
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDCUdJXVaO67S1rtsRAnjxA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ricardo Loureiro wrote:
| As part of the final project for my graduation in Informatics
| Engineering (kinda Computer Science but that's the official name),
| I'm gonna develop a "distributed" portage so we can have a test
| lab at our uni with Gentoo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
| On Tuesday 23 August 2005 07:38, Brian Harring wrote:
|>So... thoughts? I'd be particularly curious about any package where
|>this wouldn't be viable.
|
|
| I believe xorg-x11 is one such package. But then, this might just be a
Brian Harring wrote:
I don't recall having kde/gtk crap turned on by default when I first
showed up. Maybe I'm missing something; regardless, the defaults
(which should be minimal from my standpoint) are anything but.
I think you recall wrong, then. The default USE flags have been set so
tha
Brian Harring wrote:
The thing to note is that if you're relying on negation, it's going to
bite you in the ass without efforts. A server subprofile pulling from
a parent that holds desktop cruft will be forced to either
A) reinvent the wheel (maintain their own USE list), as a sizable
chun
Chris Gianelloni wrote:
You'd have a really long list of maintenance architectures for me. Like
I said, I don't use a single machine. The idea of *any* architecture
being my "primary" one just doesn't really fit. There's also the simple
fact that it doesn't matter *at all* what the maintainer
Thierry Carrez wrote:
The first Gentoo Council meeting will be held Thursday, September 15th,
at 1900 UTC.
And the place?
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
Simon Stelling wrote:
Additionally, the mentoring period should be shortened to two weeks if an AT
wants to take the end quiz to become a developer, assuming he has been AT for
at least two weeks. Users which want to become developers should also run
through the process of an AT. The amd64 portin
Mike Frysinger wrote:
- in the case of developers who do not wish to follow accepted
policies/guidelines/etc even after being enlightened, devrel is notified and
takes appropriate corrective action
- in the case of a need to take appropriate corrective action, devrel
gets tied up in investiga
Mike Frysinger wrote:
this side note is unrelated to the point being made and really belongs in the
previous discussions on the devrel list
besides, is this a bad thing ? i'd prefer to have devs settle crap themselves
than ever contacting devrel :P
It's very relevant, because it supports th
Mike Frysinger wrote:
QA team identifies a misbehaving dev who refuses to change and then hands off
the name/relevant data to devrel ... QA team then is pretty much done with
the issue and the rest is up to devrel to resolve
I disagree that devrel should be involved. I think QA should hand off
Mike Frysinger wrote:
so your previous off-topic comment about redtape in devrel processes was
irrelevant :P
Not really, because my opinion that devrel shouldn't be involved is not
automatically turned into reality (much to my regret). I'm trying to
supply evidence why this should stay betwee
Jason Stubbs wrote:
On Wednesday 14 September 2005 05:43, Donnie Berkholz wrote:
QA can work faster since it's less objected do and doesn't need endless
committees and documentation -- the documentation is the broken code.
That's not true. The documentation is the devel
1201 - 1300 of 1428 matches
Mail list logo
