From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: Re: RFC: New build types
Date: Fri, 21 Mar 2008 12:01:43 +0000 [thread overview]
Message-ID: <fs07mv$k5j$1@ger.gmane.org> (raw)
In-Reply-To: 47E24006.4030907@gentoo.org
Petteri Räty wrote:
> Steve Long kirjoitti:
>>>
>> I don't see how it would wreak more havoc than a novice using, eg ANT
>> from Java which s/he is comfortable with, and then further having to
>> learn BASH peculiarities when things don't fit with the eclass. But yeah,
>> the fun is what attracts me to the idea more than anything.
>>
>
> Java needs to be compiled and ant is meant to be started from the
> command line. Of course you can invoke the main method from Java but
> what's the point? Developers have to be able to review ebuilds and
> having all those different languages would make the job harder and I
> don't really see benefits. If you need something bit more complex done
> in an ebuild, you can always use something like inline python.
>
Yeah, sorry I haven't used Java seriously since 1.1 (apart from some MIDP
stuff) so haven't used ANT. I'm thinking more in terms of how Java was
touted as network code, similar to tcl (which is one scripted setup I would
be interested in.) So where you have a VM already instantiated, along with
whatever SecurityManager and so on, you have a framework for user, shared
or system installs, according to privilege level, with dependency
resolution handled by the package manager. (The dependencies don't have to
be confined to what the language knows about.)
You're right though, that's not of so much interest for stuff where you
already have ebuilds with associated shell infra, which you're used to
maintaining.
Thanks,
igli.
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-21 11:55 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 ` [gentoo-dev] " Steve Long
2008-03-20 5:13 ` 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 ` Steve Long [this message]
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='fs07mv$k5j$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