public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jason Stubbs" <jasonbstubbs@mailandnews.com>
To: <gentoo-portage-dev@gentoo.org>
Subject: RE: [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page
Date: Sun, 7 Dec 2003 10:44:09 +0900	[thread overview]
Message-ID: <004901c3bc63$9c47ef10$9601a8c0@jason01> (raw)
In-Reply-To: <20031206194112.GA8713@cerberus.oppresses.us>



-----Original Message-----
From: Jon Portnoy [mailto:avenj@gentoo.org] 
Sent: Sunday, December 07, 2003 4:41 AM
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] portage-ng concurse entry Was: Updated
Portage project page


On Sat, Dec 06, 2003 at 12:35:11PM -0700, Daniel Robbins wrote:

> For backwards compatibility with existing ebuilds, yes we will 
> probably still need the metadata cache since we'll still have some 
> kind of bash linkage. It's important to point out that the design of 
> portage-ng will not be tied to ebuilds. Ebuilds will likely become 
> "legacy" build scripts that are superceded by something a lot better, 
> cleaner, powerful and also faster for portage-ng.
> 

Please keep in mind that a significant number of users have expressed a 
fondness for ebuilds precisely because they can apply simple bash 
scripting knowledge to create a complex build script. Any new format 
should probably aim for similar syntax for precisely that reason.

(But this is getting way ahead of things.)

---- Jason Stubbs is writing:

It's not getting ahead of things! That's a requirement that's not
covered yet. "Package definition should be powerful but simple with a
small learning curve" or something to that effect.

Regards,
Jason Stubbs


--
gentoo-portage-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-12-07  1:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05  9:58 [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page George Shapovalov
2003-12-05 12:26 ` Paul de Vrieze
2003-12-05 21:33   ` George Shapovalov
2003-12-06 14:26     ` Paul de Vrieze
2003-12-06 19:35       ` Daniel Robbins
2003-12-06 19:41         ` Jon Portnoy
2003-12-07  0:13           ` [gentoo-portage-dev] ebuild strengths/weaknesses Daniel Robbins
2003-12-07  1:44           ` Jason Stubbs [this message]
2003-12-07  2:39             ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page George Shapovalov
2003-12-07  3:12               ` Jason Stubbs
2003-12-07  4:50               ` Ray Russell Reese III
2003-12-07  7:27                 ` Daniel Robbins
2003-12-07  7:40               ` Daniel Robbins
2003-12-07  9:11                 ` Kapil Thangavelu
2003-12-07 11:11                   ` Paul de Vrieze
2003-12-08 16:03                 ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page, ebuild conversion Sandy McArthur
2003-12-07 11:05         ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page Paul de Vrieze
2003-12-07 19:59         ` Philippe Lafoucrière
2003-12-07 20:10           ` Philippe Lafoucrière
2003-12-07 20:12           ` Jeff Smelser
2003-12-07 21:01             ` [gentoo-portage-dev] gpg signing of Manifests Douglas Russell
2003-12-07 21:53               ` Douglas Russell
2003-12-06 23:00       ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page George Shapovalov
2003-12-07 11:18         ` Paul de Vrieze
2003-12-05 16:54 ` [gentoo-portage-dev] portage-ng design competition -- not yet Daniel Robbins
2003-12-05 20:35   ` George Shapovalov
2003-12-05 21:59   ` [gentoo-portage-dev] portage-ng wish list Sandy McArthur

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='004901c3bc63$9c47ef10$9601a8c0@jason01' \
    --to=jasonbstubbs@mailandnews.com \
    --cc=gentoo-portage-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