From: "Philippe Lafoucrière" <lafou@wanadoo.fr>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] New ebuilds
Date: 19 Sep 2003 11:51:45 +0200 [thread overview]
Message-ID: <1063965105.3362.12.camel@biproc> (raw)
hey devs
Don't kill me too soon... but I really find the way to post new ebuilds
too complicated. I went to bugs.gentoo.org, and got a :
"The 'bug number' is invalid. It is neither a bug number nor an alias
to a bug number. If you are trying to use QuickSearch, you need to
enable JavaScript in your browser. To help us fix this limitation, add
your comments to bug 70907."
Of course, javascript is enable on my Mozilla Firebird :(
then, I expect nobody is working on the same ebuild as me (a python
module to do some fuzzy logic...).
It's really hard to add the new ebuild. I had to go through the maze of
bugs.gentoo.org. There's no REAL place to add them (no category for new
ebuilds). This part is really "fuzzy" too in
http://www.gentoo.org/doc/en/gentoo-howto.xml with just a link to
bugs.gentoo.org.
I think this should be really simpler, with maybe a new web repository
to upload ebuilds (I know, bugs.gentoo.org is one, but it's too heavy).
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-09-19 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 9:51 Philippe Lafoucrière [this message]
2003-09-19 10:02 ` [gentoo-dev] New ebuilds Philippe Lafoucrière
2003-09-19 10:13 ` Georgi Georgiev
2003-09-19 11:42 ` Philippe Lafoucrière
2003-09-19 10:13 ` Georgi Georgiev
2003-09-19 10:47 ` Patrick Kursawe
2003-09-19 11:42 ` Philippe Lafoucrière
2003-09-19 11:54 ` Philippe Lafoucrière
-- strict thread matches above, loose matches on Subject: below --
2005-10-24 16:09 Rafael Fernández López
2001-07-20 3:27 [gentoo-dev] new ebuilds Parag Mehta
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=1063965105.3362.12.camel@biproc \
--to=lafou@wanadoo.fr \
--cc=gentoo-dev@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