public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vano D <gentoo-dev@europeansoftware.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] emerge with interacitve use
Date: 30 Apr 2003 01:26:18 +0200	[thread overview]
Message-ID: <1051658778.17173.27.camel@gentoo.europeansoftware.com> (raw)
In-Reply-To: <200304292236.07561.panard@inzenet.org>

On Tue, 2003-04-29 at 22:36, Panard wrote:
> Le Mardi 29 Avril 2003 22:12, Vano D a écrit :
> | Hi Panard,
> |
> | 	How about adding a little functionality to the script so it keeps which
> | USE vars the user chooses in a file like
> | /var/db/pkg/app-editors/vim-6.1-r21/USECUSTOM (that would be for vim :)?
> | 	I have checked the USE files but they all contain the complete $USE
> | variable when the package was emerged. So maybe if you add the
> | functionality so it adds a USECUSTOM file containing the USE vars the
> | user has chosen interactively then you could have an option at the
> | beginning of the interactive command asking:
> |
> | 	"Use previous USE flags for this package? (X gtk etc..) [Y/n]"
> |
> | 	If the user says Y, then you would extract the USE flags from USECUSTOM
> | and use those.
...
> | 	This solves the scalibility problem and gives the user best of both
> | worlds. What do you think?
> 
> 
> Yes, I think that it's a really good functionnality to add! I will tried to 
> find a way to do this... (but some help will be welcome, I just discover 
> Python!)
> 
> Thanks for your interest !

If I knew Python and had some time I would help. Although I will have
both soon hopefully. I think great things can be achieved with extending
Portage a little bit. So I think you did a great job with this.

Also one other idea I had in mind which I would like to work on one day
is the use of a database to keep all the /var portage information for
different machines in a network and somehow extend Portage to interface
with this database and use one central emerge command (probably with a
wrapper script) to administer all these machines. For now it's all
theory of course :)

BTW just added a reply-to header.

Regards.

-- 
Vano D <gentoo-dev@europeansoftware.com>


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-04-29 23:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 18:34 [gentoo-dev] emerge with interacitve use Joshua Brindle
2003-04-29 18:53 ` Henti Smith
2003-04-29 19:12 ` Panard
2003-04-29 20:12   ` Vano D
     [not found]     ` <200304292236.07561.panard@inzenet.org>
2003-04-29 23:26       ` Vano D [this message]
2003-04-29 23:31     ` Panard
2003-04-30  0:31       ` Todd Berman
2003-04-30  0:39       ` Vano D
2003-04-30 19:50         ` [gentoo-dev] [update] " Panard
2003-04-30 22:52           ` Panard
2003-05-01  0:22             ` Daniel Armyr
2003-05-01 12:50               ` Panard
2003-05-05 12:18                 ` Panard
2003-04-30  0:18     ` [gentoo-dev] " Daniel Armyr
2003-04-29 20:15 ` Vano D
  -- strict thread matches above, loose matches on Subject: below --
2003-04-29 17:03 Panard
2003-04-29 17:34 ` Tony Clark
2003-04-29 17:30   ` Henti Smith
2003-04-29 20:03 ` Eric Noack
2003-04-29 20:27   ` Panard
2003-05-01 16:18     ` Mark Bainter
2003-04-29 20:49 ` Sergey Kuleshov
2003-04-29 21:31   ` Camille HUOT
2003-05-01  8:59 ` Nick Jones

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=1051658778.17173.27.camel@gentoo.europeansoftware.com \
    --to=gentoo-dev@europeansoftware.com \
    --cc=gentoo-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