[gentoo-dev] Updated Development HOWTO

[gentoo-dev] Updated Development HOWTO

[Daniel Robbins]

Hi All,

Just a quick note that our Development HOWTO has been significantly improved.
All interested parties should give it a read.  It's not completely upgraded
yet, but there's probably about 1500 words' worth of completely new and totally
up-to-date content.  To read it, head over to http://www.gentoo.org and then
click on "Development HOWTO" on the left-hand link bar, under "Developer
Docs:".  I think you'll enjoy the meatier approach I'm taking with this new
revision of the HOWTO.

Happy Reading,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Updated Development HOWTO

[Aron Griffis]

Hi Daniel,

A couple comments regarding the new Development HOWTO:

* ipv6 isn't listed as an available use clause

* I've been using some different syntax for use, it just seems more
  natural to me.  I don't know if others would find this helpful:

    use gnome || myvar=--disable-gnome
	or
    use gnome && myvar=--enable-gnome

* I think it would be worthwhile to rework the examples to use die
  instead of try.  Btw, assert_true_or_die is pretty long.  If you want
  to change it to something shorter, that's fine ("success_or_die" comes
  to mind).

* The list of private scripts and commands needs descriptions.  (In
  particular, I'd like to understand what benefit there is to some of
  the abstractions.)

I realize that you might not personally have time to work on all these,
but I figured I would mention them to raise awareness.  If I have time,
I'll try to contribute some docs also.  :-)

Aron

Re: [gentoo-dev] Updated Development HOWTO

[Daniel Robbins]

On Sun, Aug 12, 2001 at 11:24:49AM -0400, Aron Griffis wrote:
> Hi Daniel,
> 
> A couple comments regarding the new Development HOWTO:
> 
> * ipv6 isn't listed as an available use clause

The USE list is outdated and hasn't been updated yet.  We also need better
descriptions.

> * I've been using some different syntax for use, it just seems more
>   natural to me.  I don't know if others would find this helpful:
> 
>     use gnome || myvar=--disable-gnome
> 	or
>     use gnome && myvar=--enable-gnome

That *is* better syntax.  It should be added to the HOWTO. :)

> * I think it would be worthwhile to rework the examples to use die
>   instead of try.  Btw, assert_true_or_die is pretty long.  If you want
>   to change it to something shorter, that's fine ("success_or_die" comes
>   to mind).

Agreed.  I only got to part of the HOWTO last night.

> * The list of private scripts and commands needs descriptions.  (In
>   particular, I'd like to understand what benefit there is to some of
>   the abstractions.)

Sometimes, the abstractions are a huge benefit, and sometimes they are just a
method of allowing the user to avoid having to type ${D} in the destination.
One thing that I would be interested in is having you take a look at these
special scripts and see what you can do to enhance them or even replace them
with newer, better commands.  I think you'd be an ideal person to do this.  We
need to get you a developer account, if you'd like one.  We'd like you to have
one :)

> I realize that you might not personally have time to work on all these,
> but I figured I would mention them to raise awareness.  If I have time,
> I'll try to contribute some docs also.  :-)

That would be great.

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Updated Development HOWTO

[Aron Griffis]

Daniel,

Daniel Robbins wrote:	[Sun Aug 12 2001, 03:44:59PM EDT]
> Sometimes, the abstractions are a huge benefit, and sometimes they are
> just a method of allowing the user to avoid having to type ${D} in the
> destination.  One thing that I would be interested in is having you
> take a look at these special scripts and see what you can do to
> enhance them or even replace them with newer, better commands.
> I think you'd be an ideal person to do this.  We need to get you
> a developer account, if you'd like one.  We'd like you to have one :)

I didn't respond immediately, but if you would like to give me
a developer account, that would be fine.  :-)

I don't know what team at this point, probably the system team since
I'll be concentrating on emerge and friends for a while.

Thanks,
Aron