it.
Regards,
blubb
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
to this discussion. To solve this
problem, it will take 3 people to spend 15 minutes on a quiz they don't
like. Or it will take many more hours to discuss it over and over again.
Sorry, but this looks a bit ridiculous to me.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL
Ioannis Aslanidis wrote:
Maybe just that Developer sounds prettier than Staff. The rest is
exactly as you stated. Now let me ask developers this:
Does it really matter you if we are called developers instead of staff?
No, why should anybody bother?
--
Simon Stelling
Gentoo/AMD64
are
deprecated for over a year now.
There are also some cascading profiles which are really old and probably
should be removed.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Timestamps in the log are UTC+2, for those who wonder.
Enjoy,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
Jul 02 20:03:51 * blubb has changed the topic to: Prerelease stages in pitr:/releases/2005.1 DO NOT DISTRUBUTE | Please test gentoo-sources-2.6.12-r2 | http://uberslacks.com
Blocker: This bug prevents a software application from testing and use.?
Or what about Critical: The software crashes, hangs, or causes you to
lose data.?
Perhaps I should file a blocker bug about this ;)
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev
,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
.
Please don't make portage a news reader.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
speak at least broken English, or
they just use google translations/babelfish co. Translating bugs is
just a waste of time to me. And having a localized bugzilla with a fat
note Please write your bug report in English! is just ridiculous.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co
Mike Doty wrote:
Everyone welcome our newest minion: MetalGOD. Luis joins us to help out
with the printing herd and amd64 keywording. He also has his eyes on
the GDP project. I'll let him introduce himself.
may ekeyword be with you! welcome!
--
Simon Stelling
Gentoo/AMD64 Operational Co
?
Personally I don't know a good reason either for or against a change. I
can't see how one would be confused with different names, so I'd suggest
just leave everything as is. If you're going to make the change I won't
stop you, as long as you don't ask me to do it ;P
Regards,
--
Simon Stelling
Jason Stubbs wrote:
Personally, I think adding FEATURES to USE_EXPAND is terrible. Portage
features are not ebuild features. How much do you like C code that has
#ifdef's for the compiler being used? It's the same thing.
what wrong with #ifdef __cplusplus__? ;)
--
Simon Stelling
Gentoo/AMD64
). What should I do?
Try emerge --metadata, though i'm not sure if it really helps.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Grant Goodyear wrote:
Now that we have a new council that (I hope) will be active in approving
or rejecting GLEPs, perhaps someone should be writing a GLEP about
combining x86 and amd64?
I'm not sure if it's really worth writing another GLEP for an april's fool...
--
Simon Stelling
Gentoo
Simon Stelling wrote:
Grant Goodyear wrote:
Now that we have a new council that (I hope) will be active in approving
or rejecting GLEPs, perhaps someone should be writing a GLEP about
combining x86 and amd64?
I'm not sure if it's really worth writing another GLEP for an april's
fool
died ;)
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
gets seems far bigger.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Ciaran McCreesh wrote:
No, there was an April Fool's joke.
Which pretty good shows how ridiculous such a merge would be...
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Danny van Dyk wrote:
Paul de Vrieze schrieb:
| I agree with this. It should also be a simple, backwards compatible
| solution. Just don't call it maintainer, but maint or something like
| that ;-)
In case this should really be done, please call it 'stable'...
so we get ~stable? ;)
--
Simon
there still could be a not yet
discovered bug, right?
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
~arch in the real world, and we're not yet living in an ideal
world.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
of them got closed a day later.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Hi all,
This has been in the todo-list for quite a while, but finally it's done. I'm
curious what you think of it.
Have a nice day,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
GLEP: 41
Title: Making Arch Testers official Gentoo Staff
Version: $Revision: 1.1 $
Last
the amd64 herd does for quite some time anyway, but apparently there
are people who don't want to become developers with commit access, so that
doesn't mean we'll loose all ATs ;)
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
doesn't
make sense for *every* herd, and should be handled on a per-herd basis anyway.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Aug 23, so I think it definitively is.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
,
every user who wants to become a amd64 developer, has to become AT first, to
prove himself, so the problem you're speaking of was fixed, not caused by ATs.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
themselves.
I don't remember that being asked for...
As the GLEP asks to make the ATs staff, it'd imply giving them voting
privileges.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
is for.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
a
longer testing period, even if they work flawlessly. Or would you mark gcc 4.0
stable after 30 days? I think that's what Paul wanted to say.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Ciaran McCreesh wrote:
There is nothing in this view that says consulting the package
maintainer is not part of the stable decision-making process for arch
teams.
So do I have to ask the maintainer first everytime I want mark a package stable?
Is that what you are currently doing?
--
Simon
or portage.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
be the primary location to get information.
Other than that, i like your idea, and surely won't stop you :)
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Simon Stelling wrote:
So basically,
the documentation shouldn't be the primary location to get information.
s/shouldn't/should
I really shouldn't write emails before waking up :/
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
What would we gain with such a change? You have two tools installed that are
nearly equal, so why would one want to have two of them?
*me scratching head*
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
care to remove nano. And about xine/mplayer,
they're pretty different as well. I'm surely not stopping you from implementing
your idea, I just lack to see a real benefit.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Yay! Another member of the Swiss conspiracy!
Welcome to Gentoo, Luca
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
to his lazyness, that's not our
problem. Of course they will still bitch, so let's introduce RESOLVED RTF_ML_.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
be nice to give the ATs a @g.o address, but it's
really not essentially for me to work.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
/whatever)? There are devs who don't have commit permissions to
any cvs repo, how is their activity tracked?
In the AT case it wouldn't be so hard to check their activity. !seen on IRC and
a bugzilla query printing out bugs where they made a comment should be enough, IMHO.
--
Simon Stelling
;)
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
Harald van Dijk wrote:
(Note that I'm not going to argue either way whether this is a good
thing; I'm merely pointing out that the docs do say we're about choice.)
You still can choose between stage3 and stage3+GRP without having to do anything
but following the handbook :)
--
Simon Stelling
Albert Hopkins wrote:
Now all-of-the-sudden MySQL 5 is marked -amd64 so now I must downgrade.
Is this intentional?
read the changelog, it says:
24 Nov 2005; Jory A. Pratt [EMAIL PROTECTED] mysql-5.0.15.ebuild,
mysql-5.0.16-r3.ebuild:
version 5 does not work on clean install
--
Simon
Is there a good reason for sending this to -dev? You basically complain
about the way the GWN authors handled the issue, so why do you tell it
all the devs? It seems a bit like a lame attempt to blame them in public
for their faults.
Other than that, I agree with you.
--
Simon Stelling
Jakub Moc wrote:
:0:
* ^From:[EMAIL PROTECTED]
/dev/null
What a poor flame. Read through the flaming guide [1] twice, and try again.
[1] It once was http://dev.gentoo.org/~chriswhite/flame.html, where has
it gone?
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED
.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
... or is it a default nowadays, I'm not even sure.
You're mixing up 'strict' with 'stricter'.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
their decision what their defaults look like.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-dev@gentoo.org mailing list
and convenient, so what exactly is the
problem? It's not like you can't get Gentoo running without a network
connection anymore.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
and AMD k6 based systems.
I'm sure I'm not the only one who is using a pentium mmx as a router, so
you better think twice about it :P
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
then.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
layer that seems just redundant.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
Good luck with all the things you will be doing in future... You will be
missed.
--
gentoo-dev@gentoo.org mailing list
a list based on their input.
Check out these packages [1] before doing that, they will probably
supply all you need.
[1] http://packages.gentoo.org/search/?sstring=cpuinfo
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
.
(and if we did everything right, they would be completely identical)
Now, if you said o32, n32, and n64
[x] You just made a fool of yourself.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
him a warm welcome!
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Alec Warner wrote:
Haha, there are times when you need to realize that it's just joking
around, versus an actual flamefest ;)
This makes Gentoo look very unprofessional. It even makes us look like
we're having fun.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev
DEPEND, for which this is true: gtk was
installed with a binpkg and those don't pull in their DEPENDs because
the package is already built. For RDEPEND you can savely rely on
implicit dependencies, in most cases at least.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev
Mike Frysinger wrote:
(how do you measure the degree of a change ?)
By the number of inflammatory mails it causes within the timeframe of
two weekdays. Quite obvious, isn't it? ;)
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
.
I don't mind the council touching the metastructure, as long as they do
it right ;) If they don't, I will surely state so and ask for a
referendum. If it turns out that like 60% of the devs don't share the
council's opinion I'm sure they will re-think their decision.
--
Kind Regards,
Simon
Uhm, what kind of metadata are we talking about here? Descriptions can
just be placed in comments above the group specification line, no?
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Uhoh, forgive me for not reading the other replies before writing a
completely redundant one.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Piotr Jaroszyński wrote:
Just for fun(=I wouldn't use it in ebuild/eclass):
Sorry, but this mailing list is not really the best place for just for
fun bash foo. I suggest you take it somewhere else.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
USE_EXPAND.
For any objections, suggestions for a better name, etc. please also see
bug 139884: http://bugs.gentoo.org/show_bug.cgi?id=139884
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
on such things. Thank you, and have
a merry Christmas.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
.
I doubt so, to be honest.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
://bugs.gentoo.org/show_bug.cgi?id=148388
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Piotr Jaroszyński wrote:
What do you think?
I think it would be much nicer to have a VCS with support for atomic
commits.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
I like the idea. Something really useful I could think of is *drums*
the implementation of GLEP 42.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Hi,
This was discussed before, and noone was against it as it seems:
http://article.gmane.org/gmane.linux.gentoo.devel/44932/match=cameras+use+expand
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
Ciaran McCreesh wrote:
Which is all very well, but not sufficient reason to screw up a project
that is developed and used by a lot of people.
As if we were all gonna die without bash arrays in our config files.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org
Ciaran McCreesh wrote:
* devmanual. Not converting it over to a new shiny XML thing or
whatever, but just extending and reworking the parts that need it.
Last year's SoC FAQ said that the actual work would have to be coding,
not writing documentation.
--
Kind Regards,
Simon Stelling
Gentoo
,
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
#
# Original Author: Simon Stelling [EMAIL PROTECTED]
# Purpose: Providing a template for the app-emulation/emul-linux
, which is both
stupid and confusing.
cp -a ${S}/* ${D}/ || die copying files failed!
For future *BSD compatibility (yes i want to use the linux bsd emulation
for flash, opera, etc) it's better to use rsync -a imho
I'll use cp -pPr.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
Simon Stelling wrote:
I'll use cp -pPr.
Actually -dpPR, which is what -a is an alias for.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
really installs files with a newline character in its name,
well, then that package is just not worth including in emul-packages.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
Mike Frysinger wrote:
replace that with:
xargs -d $'\n'
aye, that looks way better.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
Simon Stelling wrote:
[snip crap]
Actually, ignore me, there's a fundamental flaw in my thinking.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
William Hubbs wrote:
Where do I find information on how to fix the package?
If you don't have a box using a multilib profile (I guess the user who
filed the bug was using an AMD64 box), you won't be able to reproduce
it. Just reassign the bug to [EMAIL PROTECTED], we'll fix it :)
Regards,
Daniel Robbins wrote:
And it should be one (web) page.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
--
gentoo-dev@gentoo.org mailing list
, which is why it is policy.
Except that in many European countries you can't even re-assign your
copyright. Oops.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
--
gentoo-dev@gentoo.org mailing list
Ciaran McCreesh wrote:
I find it amusing that no-one complaining about this has actually asked
to see it.
I think ferringb did, just not very successfully.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
--
gentoo-dev@gentoo.org mailing list
say putting
together version 2 of a spec before version 1 was writte is sane. So we
need the EAPI=0 spec. Makes it pretty easy to figure out why this spec
is fairly important.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
--
gentoo-dev@gentoo.org mailing list
.
^
It's still Europe :P --'
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
!
|
| Code listing 1.6: Usage of plurality
| email: Stop wasting our time!
[1] http://dev.gentoo.org/~chriswhite/docs/flame.html
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
--
gentoo-dev@gentoo.org mailing list
always have a
| consensus for whatever decision we reach.
Who is we in this? I assume it's devrel, but I think it should be
written out.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
--
gentoo-dev@gentoo.org mailing list
just great. I don't see why we have to
dissect every word, especially since it makes it so easy to not to see
the wood for the trees. The goal of the CoC is fairly vague ('getting
along well'), so why is there a need to specify the way ulta-explicit?
--
Kind Regards,
Simon Stelling
Gentoo
clutter up the home unnecessarily :)
--
Kind Regards,
Simon Stelling
Gentoo/AMD64
--
gentoo-dev@gentoo.org mailing list
way is google, IMHO.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-portage-dev@gentoo.org mailing list
the lines starting with said prefix out of the file, and the user could
remove old comments in the same go.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
gentoo-portage-dev@gentoo.org mailing list
came to #g-portage and
asked whether FEATURES='usersandbox -sandbox' resulting in sandbox enabled is
expected behaviour or not. Before we add usersandbox to the default FEATURES we
should make sure that -sandbox always disables sandbox.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
bugs or so :/ It would be nice if we could make
the needed decision and then close the bugs where it is NOTABUG/INVALID/LATER. I
hate stale bug listings ;)
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-portage-dev@gentoo.org mailing list
not that complex...
Bug: Split CONFIG_PROTECT into separate installing and uninstalling options
(nuke untouched files)
http://bugs.gentoo.org/show_bug.cgi?id=8423
The classical one with a huge CC list. Whatever decision is made, this finally
needs to get (fixed and) closed.
--
Kind Regards,
Simon
I'm all for it. How about 'virtual/config-manager'?
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-portage-dev@gentoo.org mailing list
cleanup will introduce many bugs, and if there are
any, it should be pretty easy to fix them.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-portage-dev@gentoo.org mailing list
for 2.2?
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-portage-dev@gentoo.org mailing list
)* implicitly, you open up potential issues like above.
Nonissue, really.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-portage-dev@gentoo.org mailing list
101 - 200 of 211 matches
Mail list logo
