come in as a news item whenever they do
update.
It almost makes you wonder whether portage-2.1.9 should run lafilefixer
itself in postinst, just to ensure everything's fixed on the system
before it starts fixing individual new packages.
--
Thanks,
Donnie
Donnie Berkho
flag implicitly endorses building bundled
code as an OK thing to do. Why is it an option at all, local or
otherwise?
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgpKR6xVx2BJM.pgp
Description: PGP signature
eversing the logic when people use the !flag syntax.
> local vartrue=${3:-${USE_SCONS_TRUE}}
> local varfalse=${4:-${USE_SCONS_FALSE}}
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgpmj3AYH1Q1S.pgp
Description: PGP signature
the same loop.
> RDEPEND="${RDEPEND}
> || ( $SELFDEPEND )
> $PHPDEPEND"
Is that || valid syntax if only one token is in SELFDEPEND? Is it
possible for an ebuild to use this eclass without setting USE_PHP?
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgpJJDphXIOwu.pgp
Description: PGP signature
tails of twisted.
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgphwsc3ER0b3.pgp
Description: PGP signature
On 20:26 Wed 06 Oct , Michał Górny wrote:
> On Wed, 6 Oct 2010 12:52:33 -0500
> Donnie Berkholz wrote:
>
> > > local flag=${1}
> > > local varname=${2:-${flag#!}}
> >
> > Could you explain how this works to me, please? It seems like you're
On 07:35 Fri 08 Oct , Michał Górny wrote:
> On Thu, 7 Oct 2010 22:08:30 -0500
> Donnie Berkholz wrote:
>
> > So what happens if I want the !use syntax and say `use_scons !ssl
> > nossl`?
>
> ${2} is set then, and ${flag#!} isn't even evaluated.
Oh, righ
27;s removing a feature is an implementation
detail that users don't and shouldn't have to care about at all.
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgp3pDlIrCqP7.pgp
Description: PGP signature
will not be a major
burden, so don't let that hold you back.
I look forward to seeing all your cool ideas!
1. http://code.google.com/opensource/gci/2010-11/index.html
2. http://code.google.com/opensource/gci/2010-11/faqs.html
3. http://en.gentoo-wiki.com/wiki/Google_Code_In_2010_ideas
-
ting during the ebuild-processing phase
(so printing starts earlier) as the previous implementation does would
give the impression of speed.
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgpTcpmUj83hf.pgp
Description: PGP signature
On 23:19 Mon 25 Oct , Donnie Berkholz wrote:
> Based on our participation in the Summer of Code, Google invited us to
> apply for their revived program for 13-18 year olds called Google
> Code-In [1-2]. The basic idea is that students will complete a series of
> small tasks rat
ne skipping ChangeLog, I take it as "something so minor,
> not worth looking into at all". Quite the opposite.
I take it as "making my job as a maintainer more difficult" because it
gives me more places I have to look to track down what happened and why.
--
Thank
have
traditionally been a reasonable default set rather than a minimal set.
This gives people who don't have much experience with Gentoo a decent
chance at getting a working system on their first try. For people who
have more experience, it's not exactly difficult to change things.
--
On 09:11 Fri 29 Oct , Donnie Berkholz wrote:
> We now have 2 ideas. It's not even worth applying unless we can get
> closer to 10. If nobody puts up more ideas in the next ~6 hours, we
> won't be participating this year.
Thanks to your help, we got enough ideas just i
0
85 9
95 2
105 7
115 1
125 4
135 4
145 1
165 1
185 4
195 1
205 1
215 1
225 1
245 2
255 1
265 3
295 2
345 2
355 2
375 1
485 1
545 1
985 1
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo L
On 10:02 Tue 02 Nov , Donnie Berkholz wrote:
> Thanks to your help, we got enough ideas just in time to apply. We
> should hear Friday whether we're in.
Unfortunately we weren't accepted. This was a highly selective set
compared to GSoC -- only 20 organizations instead of 1
tof,
I see you've said you're breaking all these ebuilds but I don't see any
rationale for the change, at least in this email. Perhaps you could
explain why this level of breakage is necessary?
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgpCuy0qPluWD.pgp
Description: PGP signature
On 21:30 Sat 06 Nov , Donnie Berkholz wrote:
> On 10:22 Sat 06 Nov , Krzysztof Pawlik wrote:
> > I'm sending this patch for discussion, what it changes? The change is
> > to where the final clone of repository will be placed, it used to be
> > ${WORKDIR}/${mod
f years? Clearly breaking things is unacceptable, but I
could envision someone simultaneously updating the eclass and all
consumers.
Perhaps you could point me to the appropriate documentation, if any
exists.
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
pgppENlLMLoiu.pgp
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Lauer wrote:
>> Mongolian keyboard layout works on Ubuntu Hoary, I
>>yesterday installed. I have no mind about this problem. Any suggestions?
It would be particularly helpful if you attached the differences in the
XKB files between Ubuntu and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg KH wrote:
> Thanks for bringing this up, I was going to do so this week. I can get
> the cvs data out of the bk tree, if we want to move it anywhere else, so
> we will not loose the history (if that's an issue.) But we need to get
> moved off of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
> Anyway, any objections against moving the current USE_EXPAND out of
> make.globals and into base's make.defaults? Those using <=2.0.50* won't get
> any additions (how it is now anyway) and anybody using a stacked profile
> (whi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
> On Fri, 2005-04-15 at 00:15 +1000, Stuart Longland wrote:
>
>>At the moment, I'm used to just clicking the Reply button to send to the
>>list... however, on most lists that I participate in, Reply-To is left
>>alone, so I'm n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrea Barisani wrote:
| There's no reference to @gentoo.org and our main MX server is
rewriting @gentoo.org
| to @lists.gentoo.org every time. Are you seeing @gentoo.org in those
headers
| in the messages you are getting?
Something has changed recently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrea Barisani wrote:
> On Fri, Apr 15, 2005 at 12:52:33PM -0700, Donnie Berkholz wrote:
>>Something has changed recently. I'm no longer getting both.
>>
>>If I go back to a post from April 2 and hit reply al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Drake wrote:
> Gentoo is fairly well oriented for this kind of environment, but it's not
> brilliant. As an example, foo-3.2.1 (the latest version) is installed on my
> system, but more recently, they fixed a critical bug in the upstream CVS tre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Drake wrote:
> - I'm manually configuring a package that I want installed in ebuild-fashion.
> I know when an ebuild runs econf it passes many configure parameters to
> achieve this (installation into /var/tmp, etc.). It would be nice if I could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jochen Maes wrote:
> "electric screwdriver."
Is that what they call 'em now?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCY1wLXVaO67S1rtsRAqQ7AKDjOAu6bB5To1FXMZSoTaU7HZauAQCgoSUM
cu0oNqzJKwnBKlZqSRKhTKo=
=39jk
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Emmanuel VARAGNAT wrote:
>
> In checkfs init script, soft RAID is initialized just after LVM, but in
> some case we can have LVM build on top of soft RAID.
> Is there any interest in doing it so ?
>
> Device-mapper can do some sort of RAID but buildi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just added a couple of new xorg-x11 ebuilds. 6.8.2-r2 is a work in
progress and will soon be removed from package.mask and unleashed upon
the masses. 6.8.99.3 is a development snapshot of CVS HEAD and is part
of an occasionally released series (rough
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul de Vrieze wrote:
> Any indication on the stability of the snapshots. I'm eager to try out all
> the
> new sugar, but do want to keep a somewhat stable system.
No guarantees one way or the other, but I'm using it as my regular X.
And unless the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Goller wrote:
> do you want both on one bug or seperate bugs, from your email, you do
> want success and problems on bugs.g.o, correct? do you want hardware
> info/binary drivers used added?
Basically emerge info and xorg.conf, from which I ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
> I just added a couple of new xorg-x11 ebuilds. 6.8.2-r2 is a work in
> progress and will soon be removed from package.mask and unleashed upon
> the masses. 6.8.99.3 is a development snapshot of CVS HEAD and is par
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
> Some people have experienced font slowdowns. This is because of a
> /usr/share/fonts/fonts circular symlink that's a migration artifact. I
> just committed a fix for it, but feel free to simply delete the symlink
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
> Is the modularization going to be handled much as the KDE splits were
> handled? That is, as with KDE having both the multilithic (multi- due to
> still having multiple category packages) and split ebuilds available for
> 3.4, will xor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
> Why do you have to
> push all these improvements on the current stable line of apache (2.0.x) ? Why
> can't these changes just be used in the upcoming alpha/beta releases and
> totally
> be implemented by the time they move to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul de Vrieze wrote:
> I've found a bug (and reverted) in the matrox driver.
https://bugs.freedesktop.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCZ+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luis F. Araujo wrote:
> Nobody is forcing. I think it is better/easier to keep the package
> than tracking/adding a lot of dependencies in the ebuilds.
So you think actually knowing what packages truly depend on is a bad idea?
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan wrote:
> there were NO reports of the error that I was getting. The error report
> said I was missing a pluggin, but it didnt say which, and therefore I
> was left out in the cold to try to find the right one. So, I started
> looking through the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Marlowe wrote:
> They didn't know how they could do
> this to gentoo based on the fact that one person's gentoo was different than
> anothers.
So is one person's Red Hat from another's, if they're updating their
systems using RHN. Perhaps to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
> Are you sure you didn't miss something here? icc and amd64?
Well, "amd64" in Gentoo -- it works on em64t at least.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCacbZXVaO67S1rtsRApUcAKDKCiH9KjYQdJSC3U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Harring wrote:
> A quicky report of flies that'll be ixnayed is available at
> http://dev.gentoo.org/~ferringb/failure.xml
Thanks for making that page! I just searched it and found two packages I
cared about with wrong SRC_URI's, fixed one and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
> You aren't the first no, but the solutions to it are limited:
> - teach developers to use -kb where they should
Wouldn't it be -ko for a patch?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using Gn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
> On Sun, Apr 24, 2005 at 07:04:58PM -0700, Donnie Berkholz wrote:
>
>>Robin H. Johnson wrote:
>>
>>>You aren't the first no, but the solutions to it are limited:
>>>- teac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've just created an x11-drivers herd. This will be for external X
drivers such as the Nvidia and ATi binary drivers and x11-drm. It's also
for less common things such as mtx-drivers and kyro-drivers.
The x11 herd will continue maintaining the X11 cor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
> On Tuesday 26 April 2005 06:57, Alin Nastac wrote:
>
>>Henrik Brix Andersen wrote:
>>
>>>On Mon, 2005-04-25 at 23:34 +0300, Alin Nastac wrote:
>>>
If it is superseded by cpufreqd, why not removing it from the tree and
app
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas de Grenier de Latour wrote:
> Sure, this packages work just fine thanks to the "/usr/X11R6 ->
> ../usr" symlink, so there is no real issue with that. But i was
> wondering whether the long term goal is to get ride of this
> symlink, and if so, w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gérald Fenoy wrote:
> I would like to know if there is any GIS team (not for Gentoo
> Installation System but for Geographic Information System ...) or any
> effort on that way ?
You might want to subscribe to the gentoo-science list, where this is
mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Brix Andersen wrote:
> Hi,
>
> I'd like to propose a new global USE flag named 'logrotate' to add
> support for app-admin/logrotate (by installing logrotate config files
> to /etc/logrotate.d/).
>
> There are currently one local USE flag named
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Bergmann wrote:
> For testing purposes (see #89767) I upgraded today from
>
>x11-base/xorg-x11-6.8.2-r1
>media-video/nvidia-kernel-1.0.6111-r3
>media-video/nvidia-glx-1.0.6111-r1
>
> to
>
>x11-base/xorg-x11-6.8.99.3
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Thu, 28 Apr 2005 12:48:52 -0700 Donnie Berkholz
> <[EMAIL PROTECTED]> wrote:
> | How annoying is it for someone to remerge a package just to get a
> | logrotate file? I suggest that if you're goi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grant Goodyear wrote:
> Donnie Berkholz wrote: [Thu Apr 28 2005, 03:21:50PM CDT]
>
>>Yes. Or don't install it at all, and let people create their own. This
>>is a dumb USE flag.
>
>
> I'd say that "dumb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
> What about the unused `ebuild [ebuild] config`? Isn't that the perfect place
> for this sort of stuff? The only package that I know that uses this feature
> is mysql. There are way more possibilities.
Interesting idea.
> Iggy'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin H. Johnson wrote:
> On Fri, Apr 29, 2005 at 09:36:54AM +0900, Jason Stubbs wrote:
>
>>What about the unused `ebuild [ebuild] config`? Isn't that the perfect place
>>for this sort of stuff? The only package that I know that uses this feature
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How long are all those non-cascaded profiles going to stick around? They
make profile changes a mess for anyone who wants to do something crazy
like change default USE flags for everyone. (Who would ever need to do
that?!?!)
Thanks,
Donnie
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lorenzo Hernández García-Hierro wrote:
> Talking in terms of my collaboration with the Gentoo project, I've done
> just a very few things, within the Hardened Gentoo subproject, but I'm
> now interested in getting more involved and somewhat time becomi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> http://www.firedrop.org.uk/devmanual/
Before I read the whole thing, were you able to take anything from the
existing handbook or need to rewrite everything from scratch?
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> i just returned from a meeting with IBM which was about getting support
> for Gentoo Linux (hardware and software). The people from IBM told me
> that it's possible for Gentoo to become officially supported on IBM
> server ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
> However, my question is do you want gcc-4.0.0 bugs yet, or not? I tried
> remerging w/ gcc4 without success, and now that I see the .99.5
> snapshot out, before I go trying to upgrade to it, I'm wondering if it's
> worth my while to tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M. Edward (Ed) Borasky wrote:
> There are also some serious performance issues with I/O. Xen is a much
> better way to go in the long run. See
Did you read his post that said that wasn't an option? I hope not,
because it would be annoying if you poste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
> Umm... does that mean file the (gcc4+amd64+xorg) bugs, and he'll work with
> them, or don't file them, because it's already got known issues that need
> fixed before bug reports on that particular combo will be anything but
> additional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Walker wrote:
> Hey guys/gals,
>
> There are a sleu of C++-only libs in dev-libs that IMO belong in dev-cpp:
Why is language a good way to sort these? I think they should be sorted
by function.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alin Nastac wrote:
> Donnie Berkholz wrote:
>>Why is language a good way to sort these? I think they should be sorted
>>by function.
>
>
> prolly 'cause C++ libraries cannot be used unless your program is
> written i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Walker wrote:
> According to herds.xml, there are currently 0 maintainers.
...
> Of course being on the alias doesn't mean anything, but if you help maintain
> the fonts herd, please add yourself to herds.xml.
You are incorrectly reading it. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
> Just thought I'd mention that the archives [1] are back up for the
> trustee mailing list. Its still being worked on, but most of the talk
> from the last year should be up.
>
> Please thank Grant for sifting through the archi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Francesco Riosa wrote:
> case $(getconf GNU_LIBPTHREAD_VERSION | tr abcdefghijklmnopqrstuvwxyz
> ABCDEFGHIJKLMNOPQRSTUVWXYZ) in
Wow, what a bad way to use tr. Apparently the author's unfamiliar with
[:lower:] and [:upper:].
Donnie
-BEGIN PGP SIGN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Krzysiek Pawlik wrote:
> Use `quickpkg` before dangerous updates/merges. If something brakes -
> untar the package.
Doesn't work too well when tar's broken too. =)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCh84IXVaO67S1rt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Brix Andersen wrote:
> The current ebuild is orinoco-0.15_rc2-r2.ebuild, and the logical name
> for a CVS snapshot would, as I see it, be
> orinoco-0.15_rc2_pre20050516.ebuild, but mixing _rcX and _preY is not
> allowed by portage.
>
> I can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heinrich Wendel wrote:
> I just read this: http://www.kdedevelopers.org/node/view/1055 and think it
> explains things very well.
I blogged [1] about this the other day. It also talks a bit about
bounties, which I was actually more interested in.
It'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Mon, 16 May 2005 16:47:17 -0700 Donnie Berkholz
> <[EMAIL PROTECTED]> wrote:
> | Heinrich Wendel wrote:
> | > I just read this: http://www.kdedevelopers.org/node/view/1055 and
> | > think it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
> A much better approach would be for there to be a rescue build,
> completely independent of the stages, since it doesn't need to mirror
> them in any way. It should be extracted (self-extracted?) to something
> like /rescue a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Forman wrote:
> You are very welcome, it was a pleasure to upgrade such a critical
> piece of Gentoo, even though it required time I could have spent outside
> in the Florida sun.
Heh, that explains why I spend so much time working on Ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Walker wrote:
> Ok that's fine. A function just seemed saner than adding 1 lines patches to
> dozens of packages.
It may be easier, but upstream would appreciate us sending a patch
instead of just fixing stuff locally.
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rafael Espíndola wrote:
> I noticed that xorg-x11-6.8.2-r1.ebuild has a very big RDEPEND. For
> example, is there really a need for flex after xorg has been compiled?
Let me know once you've tested removing each thing individually, then
run every appl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rafael Espíndola wrote:
> On 5/18/05, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
>
>>Let me know once you've tested removing each thing individually, then
>>run every application in the X distribution in every configura
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> http://www.firedrop.org.uk/devmanual/general-concepts/autotools/
>
> What more would people like to see explained? Is there anything in there
> that needs changing or clarifying? Anything that's just plain wrong?
> Does it nee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Cummings wrote:
> It's a nice idea (I know I recently opened "negotiations" up with the mips
> team for access so I could close some of my open bugs against them), but the
> two problems I can see with this are: remote access tends to mean yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Beber [Gentoo] wrote:
> Xorg 6.8.99.5 really works good.
> I've see that 6.8.99.7 have been released in CVS. Did you make some test ?
No, not yet. But bumping them is pretty trivial and low priority. I do
it when I get around to it.
> [ Also, I've ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes Weiner wrote:
> Outdated ebuild reporting system
>
>
> Why
> Reporting outdated ebuilds via bugzilla is in my opinion not the best
> solution.
> An outdated port isn't really a 'bug' and so there are man
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes Weiner wrote:
> One more tab in ${BROWSER}.. And it shouldn't make more work. It should
> ease the work already there.
> Having submitted an outdated port seems to be more comfortable to me
> than checking your portrepo everyday for actuality.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corey Shields wrote:
> The question I have is what kind of content would you like to see? This may
> turn into a call for participation later, but right now we are trying to get
> a feel for what topics people would be interested in hearing and talk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonas Geiregat wrote:
> The problem is with the install -g root -o root -m 755 scheme etc ..
> command, it seems to run fine but at the end nothing is installed
If you're manually running the install command, you might need to state
that you're i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corey Shields wrote:
> On Tuesday 24 May 2005 10:25 am, Donnie Berkholz wrote:
>
>>* Improving the desktop "experience" -- how, what, when?
>
>
> You gonna be there to do this one? ;)
I wish I could, but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego 'Flameeyes' Pettenò wrote:
> On Tuesday 24 May 2005 22:44, R Hill wrote:
>
>>I like this. It could probably be done through keywording, and in fact
>>the keywords are already there (ebuild and tested)[1].
>
> TESTED is not something a simple u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Earlier today, I added pdflib-6 to the tree. Some of you may need to
accommodate this in your ebuilds. I just wanted you to be aware, so if
you got reports of things related to it suddenly breaking, you'd have a
clue.
Thanks,
Donnie
-BEGIN PGP SIG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Walker wrote:
> I agree with Lars (particulary about adding maintaining arch to metdata if
> it's
> necessary). Another alpha++.
So, let's get a way to do this. That way most concerns will be
addressed.
Thanks,
Donnie
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
> I also like alpha, but that is not what I am responding to. And I have
> to admit that I haven't followed this too closely. But the "if one arch
> stabalises..." assumption can be misleading. For example, xorg-x11
> maintai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to remove the latest xorg revision from package.mask by the end
of the week, so I'd appreciate testing on any ebuild regressions or
relatively simple fixups from anyone who has a chance to try it out.
If you've got a problem, file a bug. Don'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
>> So far as I know, sparc is fine with 6.8.99.8;
OK, but this isn't the version I was asking about ... Did ya see the
subject? =P
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCqG+NXVa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Vermeulen wrote:
> Many Gentoo developers have written articles about Linux and Gentoo on
> third-party sites. The articles page [1] was originally meant to provide
> links to those articles. However, it frequently occurs that links change
> (most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Vermeulen wrote:
> On Thu, Jun 09, 2005 at 09:35:26AM -0700, Donnie Berkholz wrote:
>
>>It would still be useful to keep the titles and other info, just
>>removing the link. Otherwise, how are people supposed to even know th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olivier Crete wrote:
> I still fail to see why everything done by Gentoo devs belongs on the
> Gentoo page. The only article that belongs on the Gentoo page is the one
> about the Enoch and how it became Gentoo.
Because it's something relevant to Linu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Vermeulen wrote:
> Many Gentoo developers have written articles about Linux and Gentoo on
> third-party sites. The articles page [1] was originally meant to provide
> links to those articles. However, it frequently occurs that links change
> (most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Drake wrote:
> Gentoo Universe can be found at http://planet.gentoo.org/universe/
>
> Currently, there isn't a great amount of difference between the two sites.
> This will change as more people give me their entire feed URL's.
Now we can star
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
> You asked for patches. Both of these are incorporated in the 6.8.99
> series, and have been around long enough that they should go into
> 6.8.2-r2 if it is going mainstream:
> https://bugs.freedesktop.org/show_bug.cgi?id=1259
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
> On Sat, 11 Jun 2005, Donnie Berkholz wrote:
>>> I'd prefer to avoid adding patches that are feature enhancements instead
>>> of small fixes, if possible. Is it a problem if we pass on those?
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
> Won't work. First it would introduce a single point of failure. If we'd
> really follow this route there has to be a role for this, not a user.
> Then how are people supposed to know about this in teh first place? I
> wouldn't exp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua Baergen wrote:
> 1) We don't want to undermine bugzilla's function. Yes, it's noisy,
> but a suitably motivated individual (to use Donnie's catchphrase) can
> find what they're looking for.
I used the word "individual" in reference to a person
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Wegener wrote:
> On Mon, Jun 13, 2005 at 06:56:43PM -0400, Ned Ludd wrote:
>
>>I'm in favor of this. Would you mind calling it package.autouse,
>>package.use.auto or are you set on .force?
>
>
> As Mike already wrote those names are too confus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark S Petrovic wrote:
> I am about to embark on a serious project and I am considering Gentoo
> as the platform. My luck with installation, on which I've spent several
> solid days, thus far has been mixed, and I'm willing to hold off believing
> it'
1101 - 1200 of 1428 matches
Mail list logo
