[gentoo-dev] User ebuilds: all developers, please read this

[gentoo-dev] User ebuilds: all developers, please read this

[Dan Armak]

Hi all,

I have taken on myself the management of incoming ebuilds from users without 
cvs accounts. The ebuilds will (for now) still be posted here.

Ebuilds go into /usr/portage/incoming. I will create low-priority, public 
unstable dev-wiki notes to the teams involved for each ebuild.

Developers should test ebuilds, classify them and move them to their new home 
(and delete them from incoming). To keep track of the situation I suggest 
that whenever a developer verifies a user ebuild, he should grab the wiki 
item (and mark it completed or not as needed).

On the mailing list, I will post std. notes as replies to the ebuilds I move 
to /usr/portage/incoming.


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] User ebuilds: all developers, please read this

[Chad Huneycutt]

Dan Armak wrote:

>Hi all,
>
>I have taken on myself the management of incoming ebuilds from users without 
>cvs accounts. The ebuilds will (for now) still be posted here.
>
>Ebuilds go into /usr/portage/incoming. I will create low-priority, public 
>unstable dev-wiki notes to the teams involved for each ebuild.
>
>Developers should test ebuilds, classify them and move them to their new home 
>(and delete them from incoming). To keep track of the situation I suggest 
>that whenever a developer verifies a user ebuild, he should grab the wiki 
>item (and mark it completed or not as needed).
>
>On the mailing list, I will post std. notes as replies to the ebuilds I move 
>to /usr/portage/incoming.
>
>
Actually, I suggest grabbing the wiki first.  Then you will know if 
someone else has claimed it.

Oh, and by the way Dan, Chad (me, aka Bab5, aka chadh) is a developer now.

Chad (chadh)

Re: [gentoo-dev] User ebuilds: all developers, please read this

[Parag Mehta]

Hi Dan,

A suggestion, 

why don't we create the directory structure in the following manner :

/usr/portage/incoming

then for each ebuild under this should be something like this :
foo@foo.com/pkg_name/foo.ebuild

so the final directory looks like this :
/usr/portage/incoming/foo@foo.com/pkg_name/foo.ebuild

so that we can hv proper contact methods for the user who has written those ebuilds as well all ebuilds by one user can remain under the same user directory.

what do you all think ??

Regards,

pm
--
Gentoo Linux Developer

Re: [gentoo-dev] User ebuilds: all developers, please read this

[Daniel Robbins]

On Mon, Jul 30, 2001 at 08:43:29PM -0600, Parag Mehta wrote:
> Hi Dan,
> 
> A suggestion, 
> 
> why don't we create the directory structure in the following manner :

[snip]

> what do you all think ??

There's nothing wrong with that solution, but probably a bit redundant
since the info is already in the comment at the top of every ebuild.
But of course, there is no one right way to set up an incoming directory.
The structure of /usr/portage/incoming is up to Dan Armak; I'll let him
arrange it as he sees fit.

Best Regards,

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

Re: [gentoo-dev] User ebuilds: all developers, please read this

[Dan Armak]

On Tuesday 31 July 2001 03:47, you wrote:
> Dan Armak wrote:
> >Hi all,
> >
> >I have taken on myself the management of incoming ebuilds from users
> > without cvs accounts. The ebuilds will (for now) still be posted here.
> >
> >Ebuilds go into /usr/portage/incoming. I will create low-priority, public
> >unstable dev-wiki notes to the teams involved for each ebuild.
> >
> >Developers should test ebuilds, classify them and move them to their new
> > home (and delete them from incoming). To keep track of the situation I
> > suggest that whenever a developer verifies a user ebuild, he should grab
> > the wiki item (and mark it completed or not as needed).
> >
> >On the mailing list, I will post std. notes as replies to the ebuilds I
> > move to /usr/portage/incoming.
>
> Actually, I suggest grabbing the wiki first.  Then you will know if
> someone else has claimed it.
>
> Oh, and by the way Dan, Chad (me, aka Bab5, aka chadh) is a developer now.
>
> Chad (chadh)
Oh! OK. Glad you've joined us. You'll probably want to grab all your own wiki 
items, then. I didn't look into names, but rather added all ebuilds into 
incoming which weren't in cvs yet.

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] User ebuilds: all developers, please read this

[Dan Armak]

On Tuesday 31 July 2001 05:58, you wrote:
> On Mon, Jul 30, 2001 at 08:43:29PM -0600, Parag Mehta wrote:
> > Hi Dan,
> >
> > A suggestion,
> >
> > why don't we create the directory structure in the following manner :
>
> [snip]
>
> > what do you all think ??
>
> There's nothing wrong with that solution, but probably a bit redundant
> since the info is already in the comment at the top of every ebuild.
> But of course, there is no one right way to set up an incoming directory.
> The structure of /usr/portage/incoming is up to Dan Armak; I'll let him
> arrange it as he sees fit.

I haven't had time to arrange things in there yet; I'll consider the options.

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] User ebuilds: all developers, please read this

[Ben Lutgens]

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

On Tue, Jul 31, 2001 at 09:48:25AM +0300, Dan Armak wrote:
>On Tuesday 31 July 2001 05:58, you wrote:
>> On Mon, Jul 30, 2001 at 08:43:29PM -0600, Parag Mehta wrote:
>> > Hi Dan,
>> >
>> > A suggestion,
>> >
>> > why don't we create the directory structure in the following manner :

That dir structure is messey. We can get contact info from the ebuild
itself



-- 
Ben Lutgens		
Sistina Software Inc.	
Kernel panic: I have no root and I want to scream

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]