Chris Gianelloni wrote:
On Sat, 2006-07-01 at 11:12 +, Duncan wrote:
For example, if we hand out CDs at conventions etc, we would have to
also hand out source CDs.
As my reply there, however, Gentoo does still have it better than most, in
that the LiveCDs contain relatively few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
Patrick McLean schrieb:
I have absolutely zero experience with catalyst, but couldn't it be made
to create a source CD ISO when it is generating the binary one? Just
make a cd with all the distfiles used in the ISO, and keep
Roy Marples wrote:
USE client server
client - just build the client - duh
server - just build the server - duh
client and server OR neither then build both.
Other packages to possably beneift
udhcp
mldonkey
samhain
bacula
boxbackup
finger, telnet and ssh are probably other
Chris Bainbridge wrote:
On 08/06/06, Jon Portnoy [EMAIL PROTECTED] wrote:
I do very much object to using any gentoo.org infrastructure or
subdomains to do so. If someone is going to tackle that, it should be
done outside of Gentoo proper. We don't need to be stuck maintaining and
supporting a
Stefan Schweizer wrote:
-fortran - Do we really need this outdated language as a default in gcc?
I am not on the toolchain team, but I _think_ the reason this is on by
default is because fortran is considered part of a standard gcc
installation (by upstream, etc).
--
gentoo-dev@gentoo.org
No, it's needlessly unfriendly to users, and encourages broken packages.
et_EE breakage should be fixed, and slowly but surely is, and as for
unreadable error messages, getting German gcc output in a German locale
is a feature, not a bug. It can indeed be a problem in bugreports, but
it's a
Christian Birchinger wrote:
I honestly think people are just bringing up the wildest things
just to find another reason to say no. It Looks a bit like
even good ideas and project have no chance when they come from
the wrong people.
Thank you, you just summed up what I have been thinking
Chris Gianelloni wrote:
On Tue, 2006-05-16 at 23:22 +0100, Stephen Bennett wrote:
This is the exact reason why I would disagree with having this profile
in the tree. It *is* going to cause more work for bug-wranglers, no
matter how many places you put warnings and notices. If the profile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harald van D?k wrote:
The only flags that are actually removed are the flags that are invalid
_by themselves_. There are cases where flags are valid because of other
flags, such as anything following -X*.
Two other problems I see with the code:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua Nichols wrote:
Patrick McLean wrote:
There is a new version at
http://dev.gentoo.org/~chutzpah/profile.bashrc that
should fix all these possible problems. Thanks for pointing them out,
Around line 77, you have:
hasme ${flag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For about a month now, we (amd64) have had some code in our
profile.bashrc that filters CFLAGS that are unrecognized by gcc, and
warnings the user about bad CFLAGS.
So far it has worked fairly well, and it has really cut down on the
number of bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Warner wrote:
Except you need a way for them to turn it off, and you do not currently
provide one. We can set default flags all we want, but I don't see
filtering 'bad' flags as necessarily our problem. If you want to say:
Hey we have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dennis Allison wrote:
Open office appears to be masked (amd64). Who would I ask to find out the
current status?
OpenOffice doesn't currently compile on 64-bit architectures, you can
use openoffice-bin, which is a 32-bit binary, on amd64 for now.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have masked dev-lisp/plt pending removal in 30 days. This has been
unmaintained for awhile (no metadata.xml) and a newer version of the
same package is in the tree as dev-scheme/drscheme.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fernando J. Pereda wrote:
On Sun, Mar 26, 2006 at 06:39:15AM +0200, Luca Barbato wrote:
git : c+bash (and optional perl/python for some merge scripts)
I think git is probably the best choice, I have played with it a little
myself and it is _very_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
On Mon, 13 Feb 2006 19:39:06 +0100 Simon Stelling [EMAIL PROTECTED]
wrote:
| Are you being serious about this?
Sadly, even if he is, there're enough people around here that're taking
that kind of thought seriously (see,
Mark Loeser wrote:
Donnie Berkholz [EMAIL PROTECTED] said:
Jason Stubbs wrote:
The patch now has the debugging output and x11-base/xorg-x11 check removed.
Excellent. Works perfectly. Since we're failing on them, perhaps we can
say obsolete instead of deprecated?
Can we put this back to
You know, I'd actually support a rather more abrupt transition,
where we announce that on a particular date all digest files are going
to be removed, thereby breaking any version of portage older than
portage-x.y.z. Many people would probably miss such a deadline, but
assuming that we also
Sven Vermeulen wrote:
On Fri, Nov 18, 2005 at 09:09:29PM -0400, Luis F. Araujo wrote:
What is the problem of giving them @g.o addresses?
Why exactly do we need the distinction? (sorry, i can't see any benefit
but more confusion).
The GLEP was originally created to help the architecture
101 - 119 of 119 matches
Mail list logo
