Re: [gentoo-dev] new use flag editor : profuse

[Georgi Georgiev]

maillog: 08/12/2004-15:50:32(+0100): dams types
> >- It removes stuff from my make.conf if it is redundand with the
> >  information from my profile. For example, if I have "alsa" in
> >  /etc/make.conf and I run profuse, it says that alsa is set in
> >  make.defaults and make.conf. I say OK, then run profuse again, and I
> >  get alsa specified in make.defaults only, because profuse removed it
> >  from make.conf. Could you implement an option that will at least give
> >  it a choice to not touch stuff that is already in my make.conf, unless
> >  I specifically request it? I mean, you do keep the data in the table
> >  anyway? Maybe if you made use flags with three states ("enabled",
> >  "disabled" and "unset") it would be trivial to write out to make.conf
> >  every flag that is not "unset". The table could then display either
> >  a "+", a "-" or nothing for each flag.
>
> Both things are possible, what do you prefer? I think the second
> solution would be more straightforward

Yep, I like the three-state solution best. Not sure how it would look in
GTK+, but I imagine something similar to the gconfig of the linux
kernel.

> >- "profuse --profile-dir=/usr/portage/profiles/default-linux/alpha/2004.3"
> >  fails because of the weirs syntax in that profile.
> >
>
> Is it weird and wrong or weird but correct (and I should try to support
> it ) ?

I hope someone answers that, but my opinion is that since the profile
works (I guess it does) it must be correct. After all, these config
files are supposed to be python-style syntax... (looks at
portage_util.py:defconfig, which uses shlex)... or not.

-- 
*)   Georgi Georgiev   *)  The only skills I have patience to learn    *)
(*    chutz@×××.net    (* are those that have no real application in   (*
*)  [phone]   *) life. -- Calvin                              *)

--
gentoo-dev@g.o mailing list