From: Todd Berman <tberman@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] emerge with interacitve use
Date: 29 Apr 2003 20:31:31 -0400 [thread overview]
Message-ID: <1051661864.7006.1.camel@phaze> (raw)
In-Reply-To: <200304300131.18918.panard@inzenet.org>
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
Please stop attaching things to emails coming to this list. Either post
a url, or ask for people to reply privately to you so you can email it
to them.
Thanks
--Todd
On Tue, 2003-04-29 at 19:31, 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.
> |
> | Also you could have a commandline option such as --usecustom or
> | something like that, so if the user calls emerge-interactive with that
> | flag it skips all questions and uses the previously kept USE flags.
> |
> | Of course this would only work if you only used emerge-interactive
> | since emerge doesnt create any USECUSTOM files :) But I don't think this
> | is a big problem. In any case if emerge-interactive doesn't find any
> | CUSTOMFILE then it asks the users for USE flags just like now.
> |
> | This solves the scalibility problem and gives the user best of both
> | worlds. What do you think?
> |
> | Regards.
>
>
>
> Ok, I've apply theses changes (I join the emerge-interactive file) :
>
> -> there is a /var/db/pkg/CATEG/PKG/USECUSTOM :
> ask to use this file y or n :
> y : we load the values of the file
> n : we ask for the new values, when, (re-)create
> /var/db/pkg/CATEG/PKG/USECUSTOM
> -> no file we do exactly like if the user answer n to the previous question
>
>
>
> Please test this script (I made some merge and it was working)
>
> Thanks,
>
> Panard
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-30 0:31 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
2003-04-29 23:31 ` Panard
2003-04-30 0:31 ` Todd Berman [this message]
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=1051661864.7006.1.camel@phaze \
--to=tberman@gentoo.org \
--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