public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Camille HUOT <cam@cameuh.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] emerge with interacitve use
Date: Tue, 29 Apr 2003 23:31:18 +0200	[thread overview]
Message-ID: <20030429233118.1422dc2d.cam@cameuh.net> (raw)
In-Reply-To: <200304292049.55847.sergey@til-design.com>

[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]

Very nice.

I think with a user interface like ufed it could be merged to the
true emerge.

Thanks for the contribution

On Tue, 29 Apr 2003 20:49:55 +0000
Sergey Kuleshov <sergey@til-design.com> wrote:

> Hey, I really like this feature! It really helps (anyway it's better
> that looking in the .ebuild file and sort out what are the optional
> dependencies.)
> 
> The thing I did not get is why is it sometimes dispalying the Disabled
> ..... text ans sometimes not?
> 
> P.S. What about enchancing it with some ncurses interface to make it
> really intteractive?
>
> On Tuesday 29 April 2003 17:03, Panard wrote:
> > Hello,
> >
> > 	After some experiencies with emerge, it could be great that to
> > 	do an
> > emerge with USE interactive :
> >
> > $ emerge -I php
> >
> > >>> ...
> >
> > Use Java [Y/n]?
> > Use X[y/N] ?
> > ....
> >
> > I found, that there are too many errors due to USE vars that we
> > forget  to disable or enable...
> >
> > So I have taken my hands and my vim, and tried to do this, it gave a
> > good result.
> >
> > I join the script, its name is emerge-interactive, this is in fact
> > the emerge script with my modifications (line  1840 to 1877)...
> > place it in the directory
> > /usr/lib/portage/bin
> > then
> > ln -s /usr/lib/portage/bin/emerge-interactive /usr/bin
> >
> >
> > To use the interactive mide, use
> > $ emerge-interactive -I or --interactive ....
> >
> > 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 !!)
> >
> > Thanks!
> >
> > Panard
> 
> -- 
> Sergey Kuleshov <sergey@til-design.com>
> Studio Programer
> Microsoft Certified Professional
> 
> --
> gentoo-dev@gentoo.org mailing list
> 


-- 
Camille HUOT - <cam@cameuh.net>
cam on #gentoofr at irc.freenode.net
public key available at http://www.cameuh.net/infos/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-29 19:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 17:03 [gentoo-dev] emerge with interacitve use 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 [this message]
2003-05-01  8:59 ` Nick Jones
2003-05-12 22:50 ` [gentoo-dev] [update] " Panard
  -- strict thread matches above, loose matches on Subject: below --
2003-04-29 18:34 [gentoo-dev] " 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
2003-04-29 23:31     ` Panard
2003-04-30  0:31       ` Todd Berman
2003-04-30  0:39       ` Vano D
2003-04-30  0:18     ` Daniel Armyr
2003-04-29 20:15 ` Vano D

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=20030429233118.1422dc2d.cam@cameuh.net \
    --to=cam@cameuh.net \
    --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