From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: New build types
Date: Thu, 20 Mar 2008 03:59:01 +0000 [thread overview]
Message-ID: <frsn01$s1m$1@ger.gmane.org> (raw)
In-Reply-To: 47DF954A.3000808@gentoo.org
Rémi Cardona wrote:
> What would be the point of such a change? What problem are you trying to
> solve or to improve?
>
First and foremost to give an environment wherein people can write their
installation scripts using the language they are most comfortable with.
Secondly efficiency; in the case of a pbuild it could be run from within the
PM; for something like a jbuild it would use the native tools and existing
libraries like ANT. For hbuild it would tie into Cabal. While these may be
used already, we go from PM -> BASH -> LangX. I'm just saying give the
_option_ to leave out the BASH bit when you have mature tools in langX.
> You'll need to answer those questions anyway should you ever need to
> write a GLEP for that.
>
Yeah, that's a long way off; no point doing a GLEP without a working
implementation to show what you mean, imo. No point dedicating coder
resource to implement if it'd never get used in any case.
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-20 3:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 10:18 [gentoo-dev] RFC: New build types Steve Long
2008-03-18 10:11 ` Rémi Cardona
2008-03-20 3:59 ` Steve Long [this message]
2008-03-20 5:13 ` [gentoo-dev] " Rémi Cardona
2008-03-20 6:51 ` [gentoo-dev] " Steve Long
2008-03-20 7:15 ` Brian Harring
2008-03-21 12:52 ` [gentoo-dev] " Steve Long
2008-03-20 10:44 ` [gentoo-dev] " Petteri Räty
2008-03-21 12:01 ` [gentoo-dev] " Steve Long
2008-03-20 5:31 ` [gentoo-dev] " Marius Mauch
2008-03-18 10:32 ` [gentoo-dev] " Jakub Moc
2008-03-18 21:23 ` Luca Barbato
2008-03-20 4:02 ` [gentoo-dev] " Steve Long
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='frsn01$s1m$1@ger.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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