From: Jose San Leandro <jose.sanleandro@ventura24.es>
To: gentoo-dev@lists.gentoo.org
Cc: Ciaran McCreesh <ciaranm@ciaranm.org>
Subject: Re: [gentoo-dev] Suggestion
Date: Thu, 8 Feb 2007 11:59:18 +0100 [thread overview]
Message-ID: <200702081159.19818.jose.sanleandro@ventura24.es> (raw)
In-Reply-To: <20070208094342.4ebaf6cb@snowdrop>
That is enough once you know how to write ebuilds.
We were thinking of a GUI to soften the learning curve to non-experts.
Probably not useful for a Gentoo developer, but could provide an easy way to
write ebuilds to project maintainers themselves, not to Gentoo resources.
On Thursday 08 February 2007 10:43, Ciaran McCreesh wrote:
> On Thu, 8 Feb 2007 10:38:08 +0100 Jose San Leandro
>
> <jose.sanleandro@ventura24.es> wrote:
> | A friend of mine and myself are willing to develop some tools to help
> | ebuild development.
>
> All the common cases should be handled by default functions, package
> manager functions and eclasses. Thus, writing ebuilds should consist
> merely of handling unique or uncommon special cases, and the best tool
> for doing that is an ebuild-aware text editor.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-08 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 9:38 [gentoo-dev] Suggestion Jose San Leandro
2007-02-08 9:43 ` Ciaran McCreesh
2007-02-08 10:50 ` Christopher Covington
2007-02-08 13:26 ` Joshua Nichols
2007-02-14 10:40 ` [gentoo-dev] Suggestion Steve Long
2007-02-08 10:59 ` Jose San Leandro [this message]
2007-02-08 12:39 ` [gentoo-dev] Suggestion Chris Gianelloni
2007-02-08 14:42 ` Luis Francisco Araujo
2007-02-08 10:40 ` Alistair Bush
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 16:44 [gentoo-dev] suggestion Andy Molloy
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=200702081159.19818.jose.sanleandro@ventura24.es \
--to=jose.sanleandro@ventura24.es \
--cc=ciaranm@ciaranm.org \
--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