From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] User ebuilds: all developers, please read this
Date: Mon Jul 30 20:59:02 2001 [thread overview]
Message-ID: <20010730205826.G27325@cvs.gentoo.org> (raw)
In-Reply-To: <20010730204329.B30944@cvs.gentoo.org>; from pm@gentoo.org on Mon, Jul 30, 2001 at 08:43:29PM -0600
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.
next prev parent reply other threads:[~2001-07-31 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 14:57 [gentoo-dev] User ebuilds: all developers, please read this Dan Armak
2001-07-30 18:51 ` Chad Huneycutt
2001-07-31 0:47 ` Dan Armak
2001-07-30 20:44 ` Parag Mehta
2001-07-30 20:59 ` Daniel Robbins [this message]
2001-07-31 0:48 ` Dan Armak
2001-07-31 8:32 ` Ben Lutgens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010730205826.G27325@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox