From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev-return-2834-arch-gentoo-dev=gentoo.org@gentoo.org>
Received: (qmail 9603 invoked by uid 1002); 1 May 2003 08:59:38 -0000
Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Help: <mailto:gentoo-dev-help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Received: (qmail 5492 invoked from network); 1 May 2003 08:59:37 -0000
Date: Thu, 1 May 2003 03:59:31 -0500
From: Nick Jones <carpaski@twobit.net>
To: Panard <panard@inzenet.org>
Cc: gentoo-dev@gentoo.org
Message-ID: <20030501085931.GA355@twobit.net>
Mail-Followup-To: Panard <panard@inzenet.org>, gentoo-dev@gentoo.org
References: <200304291903.19747.panard@inzenet.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG"
Content-Disposition: inline
In-Reply-To: <200304291903.19747.panard@inzenet.org>
User-Agent: Mutt/1.4i
Subject: Re: [gentoo-dev] emerge with interacitve use
X-Archives-Salt: 6b69b8ae-9a75-4d2d-beee-c713176a804f
X-Archives-Hash: afff73da60f6340b4b9b8b9ed50de41e

--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> After some experiencies with emerge, it could be great that to
> do an emerge with USE interactive:
>=20
> $ emerge -I php
> >>> ...
> Use Java [Y/n]?
> Use X[y/N] ?
> ....

This is an interesting idea, but can cause a lot of problems... It
has potential after 2.1 is released, but I don't recommend doing
things this way right now.

If you merge applications without a specific flag for a dependent
package, and then merge a package with that specific flag, it may
very well assume that the support you requested is there.  Little
errors may creep up on you. While this should be fairly harmless,
it might be a little annoying.

Portage will gain a lot more support for SLOTS, USE, and keywords
in the 2.1 series. It'll actually allow dependence based on a USE
setting and the child's build settings. It will remember them for
future emerges on a per-package basis as well.

> I join the script, its name is emerge-interactive, this is in
> fact the emerge script with my modifications (line 1840 to 1877)

If you make modifications to portage, I'd really appreciate it if
you would post patches on bugs.gentoo.org. It'll give me a chance
to look the changes over and give feedback as well as consider it
for integration into portage. (diff -u, greatly prefered)

> This is my first gentoo and linux contribution so I'm waiting for
> some feedback, impression, and sure critiques and amelioration
> (this is the first time I script in python, so be indulgent !!)

This one in particular I'd rather see as a front-end instead of a
direct integration like this. Sticky flags (which will show up in
2.1) will feed from the command line and will have a lot of rules
regarding how use flags are set for a session.  This method steps
around portage's ability to determine Sticky (persistant, limited
flags set for specific packages) flags. It might end up causing a
lot of rebuilding due to global use flag changes.

If you continue with integrating it, just make sure you follow the
code changes that are coming up this summer, and perhaps it might
be adopted in one form or another.

--NJ


--OgqxwSJOaUobr8KG
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+sOHyH/cWKbF87VYRAjeIAJ0YOFJb8vXE1drOzTSfSIBsINvf3gCgtZ+P
xbZZew9YXWMp7LE2UDpn0Qk=
=GAm2
-----END PGP SIGNATURE-----

--OgqxwSJOaUobr8KG--