From: Eldad Zack <eldad@stoneshaft.ath.cx>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] creating ebuilds
Date: Tue, 06 Jan 2004 19:56:40 +0200 [thread overview]
Message-ID: <1073411799.19583.5.camel@localhost> (raw)
In-Reply-To: <200401061333.03551.pauldv@gentoo.org>
On Tue, 2004-01-06 at 14:33, Paul de Vrieze wrote:
> I'm sorry for that. It however can be a sign that the tree is not ready
> for those ebuilds, or that they are in very low demand.
Perhaps we can create some sort of repository for these kind of ebuilds,
as an outlet for the low-demand ebuilds, where a user could search for
an ebuild, and not reinvent the wheel, if a package he'd like to install
falls under this category.
Searching bugzilla would yield the same results, I assume, but it's
seems to me somewhat less inviting.
Eldad
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-06 18:06 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Adlms-0007w8-Uk@smtp.gentoo.org>
2004-01-06 12:33 ` [gentoo-dev] creating ebuilds Paul de Vrieze
2004-01-06 17:26 ` Robert Cole
2004-01-06 17:39 ` Ciaran McCreesh
2004-01-06 18:01 ` Robert Cole
2004-01-06 19:26 ` Chris Gianelloni
2004-01-06 19:53 ` Peter Ruskin
2004-01-06 20:11 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2004-01-06 21:44 ` Peter Ruskin
2004-01-06 20:12 ` [gentoo-dev] " Ciaran McCreesh
2004-01-06 20:21 ` Marius Mauch
2004-01-06 20:37 ` Jan Schubert
2004-01-06 21:14 ` Chris Gianelloni
2004-01-06 21:36 ` Chris Gianelloni
2004-01-06 19:20 ` Chris Gianelloni
2004-01-06 17:56 ` Eldad Zack [this message]
2004-01-06 18:02 ` Eldad Zack
2004-01-06 18:33 ` Robert Cole
2004-01-06 19:31 ` Chris Gianelloni
2004-01-06 20:38 ` Jan Schubert
2004-01-06 20:54 ` Spider
[not found] <FILESERVERAmEaJswFC00000011@FILESERVER.aurora.local>
2004-01-06 14:57 ` Caleb Tennis
2004-01-06 8:17 Robert Cole
2004-01-06 12:57 ` Paul de Vrieze
2004-01-06 15:37 ` Seemant Kulleen
2004-01-06 18:14 ` Robert Cole
2004-01-06 20:49 ` Jan Schubert
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 7:05 Robert Cole
2004-01-06 7:15 ` Jon Portnoy
2004-01-06 7:36 ` Allen Parker
2004-01-06 7:39 ` Robert Cole
2004-01-06 7:55 ` Jon Portnoy
2004-01-06 8:39 ` Robert Cole
2004-01-06 9:54 ` Kurt Lieber
2004-01-06 13:08 ` Caleb Tennis
2004-01-06 14:13 ` Allen Parker
[not found] ` <E1Adry1-0003ZV-8m@smtp.gentoo.org>
2004-01-06 21:09 ` Spider
2004-01-07 0:24 ` Robert Cole
2004-01-07 13:36 ` Chris Gianelloni
2004-01-06 15:18 ` Robert Cole
2004-01-06 16:04 ` Chris Gianelloni
2004-01-06 16:31 ` Robert Cole
2004-01-06 16:45 ` Ciaran McCreesh
2004-01-06 17:17 ` Robert Cole
2004-01-06 19:17 ` Chris Gianelloni
2004-01-06 19:43 ` Robert Cole
2004-01-06 20:07 ` Ciaran McCreesh
2004-01-08 7:12 ` John Nilsson
2004-01-08 9:56 ` Paul de Vrieze
2004-01-08 14:36 ` John Nilsson
2004-01-08 20:53 ` Nicholas Hockey
2004-01-10 11:39 ` foser
2004-01-06 12:09 ` Chris Gianelloni
2004-01-06 15:38 ` Robert Cole
2004-01-06 19:29 ` Marius Mauch
2004-01-06 12:44 ` Paul de Vrieze
2004-01-06 15:45 ` Robert Cole
2004-01-06 20:39 ` Paul de Vrieze
[not found] ` <E1Adllq-0001dV-26@smtp.gentoo.org>
2004-01-06 7:46 ` Jon Portnoy
2004-01-06 18:56 ` George Shapovalov
2004-01-06 19:06 ` George Shapovalov
2004-01-06 19:45 ` Marius Mauch
2004-01-06 20:44 ` Paul de Vrieze
2004-01-10 11:13 ` foser
2004-01-10 12:16 ` Jason Stubbs
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=1073411799.19583.5.camel@localhost \
--to=eldad@stoneshaft.ath.cx \
--cc=gentoo-dev@lists.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