On Sat, 2005-08-20 at 19:42 -0400, Nathan L. Adams wrote:
[snip]
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 is found.
-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
Donnie Berkholz posted [EMAIL PROTECTED], excerpted below, on
Sun, 21 Aug 2005 03:02:36 -0700:
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
This time I'll say something useful :)
Nathan, you seem to be misunderstanding open source. You get the I
can ask for features or suggest things part, but not that I can add
features or do things part. No one is stopping you, or me, or an
average joe, or George W. Bush, from peer reviewing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Portnoy wrote:
I hate to be the bearer of bad news
Somehow, I doubt that... ;)
but that's because you don't realize
how many devs are sitting back and giggling at this thread 8)
I didn't realize you got together with other devs for giggle
On Sun, 2005-08-21 at 09:22 -0400, Nathan L. Adams wrote:
And yet I see scarce few ideas on how to solve the problem. The only
other person who seems to have any are Ciaran, and what is his solution?
He's doing *code reviews* of ebuilds. *GASP* Imagine that!
And - as I told you the last time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Meltzer wrote:
This time I'll say something useful :)
Nathan, you seem to be misunderstanding open source. You get the I
can ask for features or suggest things part, but not that I can add
features or do things part. No one is stopping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Brix Andersen wrote:
And - as I told you the last time you brought this issue up - you're
more than welcome to start reviewing ebuilds and commits as well.
I'm starting to do just that. I've even asked Ciaran to review a
particular ebuild I
On Monday 04 July 2005 09:26, Robin H. Johnson wrote:
I was just finally shuffling packages into the app-backup category
(originally discussed in March, but not implementing due to epkgmove
status at the time), and I wanted to put the herd into the category
metadata, but I found that we don't
On Sun, 2005-08-21 at 10:10 -0400, Nathan L. Adams wrote:
I'm starting to do just that. I've even asked Ciaran to review a
particular ebuild I was interested in so that I could learn from it.
That's still not *you* doing the actual work - that's you requesting
someone else to review your work -
On Sun, 2005-08-21 at 11:14 -0400, Nathan L. Adams wrote:
Its a chicken and egg situation. I need to have a certain level of
expertise with ebuild syntax and conventions to do the job. So I've
asked for some help from an expert. Also, I learn things quicker and
easier by first seeing examples
On Sun, 21 Aug 2005 17:20:00 +0200 Henrik Brix Andersen
[EMAIL PROTECTED] wrote:
| We have plenty of examples in portage
...some of which are good and some of which are terrible.
| Did you read our Ebuild HOWTO [1] yet?
That's, uh, not really the best documentation around... The devmanual's
a
Nathan L. Adams wrote:
Its a chicken and egg situation. I need to have a certain level of
expertise with ebuild syntax and conventions to do the job. So I've
asked for some help from an expert. Also, I learn things quicker and
easier by first seeing examples and then seeing the
I have been the lilypond maintainer for x years, but lately I haven't
been using it personally, and consequently I haven't been keeping up
with the releases. However there are lots of users that would like to
see the update go into portage.
Any devs, particularly tex-savvy ones, interested in
On Sun, 2005-08-21 at 22:05 +0100, Ciaran McCreesh wrote:
[snip good description of problem]
Now the proposal. This isn't something that can happen immediately, but
it's something I'd like to see us working towards:
* Make everything that isn't xterm set its own TERM value. Possibly the
On Sun, 2005-08-21 at 23:13 +0100, Ciaran McCreesh wrote:
The problem with this is that non-X boxes will be missing the terminfo
descriptions.
Right.
The problem with this is that some terminals gain new capabilities
fairly regularly. One example is rxvt-unicode, which is still putting
out
putty pretends to be an xterm and dies at xtermcontrol --get-bg... I
can test other things if you need.. just give me some idea :)
On 8/21/05, Ciaran McCreesh [EMAIL PROTECTED] wrote:
On Mon, 22 Aug 2005 00:00:26 +0200 Henrik Brix Andersen
[EMAIL PROTECTED] wrote:
| * Install, either with
On Sun, 21 Aug 2005 18:43:54 -0400 Dan Meltzer
[EMAIL PROTECTED] wrote:
| putty pretends to be an xterm and dies at xtermcontrol --get-bg... I
| can test other things if you need.. just give me some idea :)
Thanks. The other useful one is to see whether it does 256 colours
properly like real
On Mon, Aug 22, 2005 at 12:08:00AM +0100, Ciaran McCreesh wrote:
Thanks. The other useful one is to see whether it does 256 colours
properly like real xterm does. The following bash script, when run with
'256' as its argument, should look the same as it does when run under
a real xterm.
Not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luca Barbato wrote:
http://dev.gentoo.org/~plasmaroo/devmanual/
Thanks, I've been wondering where Ciaran's docs went. :)
Now, there one question that I won't be able to answer for myself
anytime soon:
What are the most common ebuild mistakes?
A
-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=2chap=3
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
-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
Ciaran McCreesh wrote:
On Sun, 21 Aug 2005 23:10:58 -0400 Nathan L. Adams [EMAIL PROTECTED]
wrote:
| What are the most common ebuild mistakes?
Existing tools will already get some of these. However, most
user-submitted ebuilds have quite clearly
maillog: 22/08/2005-04:25:38(+0100): Ciaran McCreesh types
On Sun, 21 Aug 2005 23:10:58 -0400 Nathan L. Adams [EMAIL PROTECTED]
wrote:
| What are the most common ebuild mistakes?
| ...
KEYWORDS, under-quoting of variables (we didn't used to care about
quoting on ${D} etc), using einstall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georgi Georgiev wrote:
When should make be used? I thought that ebuilds should always use
emake, and if necessary -- emake -j1. But never make.
make DESTDIR=${D} install || die make install failed
- --
smithj
Gentoo Developer
[ desktop stuff
On Sun, 21 Aug 2005 23:52:15 -0400 Jonathan Smith [EMAIL PROTECTED]
wrote:
| Georgi Georgiev wrote:
| When should make be used? I thought that ebuilds should always use
| emake, and if necessary -- emake -j1. But never make.
|
| make DESTDIR=${D} install || die make install failed
make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
Nathan L. Adams wrote:
| What are the most common ebuild mistakes?
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2chap=3
Thanks everyone. I'll bug each of you individually if I need clarification.
Nathan
Alec Warner wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Was talking with Brian about the build environment and how settings were
to be passed into the build environment.
Essentially three scenarios were presented.
1) The full environment is passed to the build environment. This was
28 matches
Mail list logo
