From: Joshua Pierre <joshua@swool.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] A wishlist
Date: Tue Oct 16 05:40:02 2001 [thread overview]
Message-ID: <20011016194042.B32545@swool.com> (raw)
In-Reply-To: <1003238060.8487.27.camel@zoidberg>
> > My own wishlist: Layout for a .ebuild
>
> Yes, we need a standard for layout on ebuilds. This is exactly as
> codingstandards in coding-projects. It's very important for
> maintainability.
>
> We need to write a document describing this and all developers has to
> follow this even if they might not like the syntax.
>
> I try to make all my ebuilds look the same and probably others try that
> aswell. One problem now is that no one knows who is responsible for
> which ebuilds.
>
> If we can't decide on a syntax for our ebuilds we have to make a list of
> who maintains which packages and after that people shouldn't commit on
>
Yes! Definately need this for ebuild's. However, the current documentation is
unfinished so perhaps we can set some standards and finalise the whole lot.
I will volunteer to help write documentation and possibly form the original
standards with a team of several Gentoo developers.
Just let me know if you want some help with this as I will be more than willing
to help write some documentation.
Regards,
Joshua Pierre
--
You can do it, you can do it all night long
next prev parent reply other threads:[~2001-10-16 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 10:42 [gentoo-dev] A wishlist Karl Trygve Kalleberg
2001-10-14 11:40 ` Martin Schlemmer
2001-10-16 5:12 ` Mikael Hallendal
2001-10-16 5:40 ` Joshua Pierre [this message]
2001-10-20 11:22 ` [gentoo-dev] rc6 "bash:mc" Mark King
2001-10-20 11:24 ` Daniel Robbins
2001-10-20 13:06 ` Mark King
2001-10-14 16:08 ` [gentoo-dev] A wishlist Dan Armak
2001-10-14 16:49 ` Dan Armak
2001-10-14 22:12 ` Joshua Pierre
2001-10-15 6:46 ` Chris Houser
2001-10-15 7:17 ` Joshua Pierre
2001-10-16 5:05 ` Mikael Hallendal
2001-10-16 5:29 ` Joshua Pierre
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=20011016194042.B32545@swool.com \
--to=joshua@swool.com \
--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