public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikko Husari <husku@husku.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Simplistic bash-script to manage package.use
Date: Sun, 13 Jul 2008 01:01:06 +0300	[thread overview]
Message-ID: <487929A2.1040806@husku.net> (raw)
In-Reply-To: <fbdd0e50807121442s15393ea3xd3e674657d1b0bf@mail.gmail.com>

Gentoo User wrote:
> Hi,
>
> the question is: is it really necessary? If I want to add a new entry
> into this file I just call echo "category/package myflags" >>
> /etc/portage/package.use and if I want to edit them I just call my
> favorite editor, use its search capabilities and change the line.
> So I don't really see the benefit of a command line tool, since I
> still need to write flags, package and everything and the tools I'm
> using now (mostly echo, grep and vim) to do this are not very
> complicated and most of the typing goes to the use flags and package
> name anyway.
>
>
> Just my opinion.
>
>
> Best regards
>
> Geralt
>
>
> On 7/12/08, Mikko Husari <husku@husku.net> wrote:
>   
>> greetings earthlings,
>>
>>  i did not found (nor did i look for long enough) any tools/scripts to
>> easily manage package.use file, so i did my own. now i started to think
>> that, if there really is not any, my creation would be sufficient (although
>> possibly buggy) for most users who wish to have "easy" control over
>> package.use.
>>
>>  yes, i know this is not the best place to "announce" but, this is not an
>> real announcement, this is an query for an superior solution which would
>> show my creation to be useless/dublicate/stupid. (if mine is useless/stupid
>> it would be nice, so i would not have to maintain it and i also could use
>> some real software).
>>
>>  -- husku
>>
>>
>>     
well, i cant argue with you on that. although, i also used 
vim,grep,sed,echo to change my flags. still i felt i needes an easier 
way, thats why i wrote it and thats why i think this is "easier" than 
vim+handwork. basicly that script is only an interface to sed,echo,grep 
and equery.

did you try to use it? id bet i could get changes applied much more 
rapidly with that script than with vim or echo. (can not necessarily 
compete with echo if you are sure it is an new addition)
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-07-12 22:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-12 21:19 [gentoo-user] Simplistic bash-script to manage package.use Mikko Husari
2008-07-12 21:42 ` Gentoo User
2008-07-12 22:01   ` Mikko Husari [this message]
2008-07-13 10:38     ` Gentoo User
2008-07-13 10:48       ` Mikko Husari
2008-07-13 15:19         ` Alan McKinnon
2008-07-13 16:07       ` Neil Bothwick
2008-07-14  0:19         ` Gentoo User
2008-07-14  0:21           ` Neil Bothwick
2008-07-13 11:29 ` Arttu V.
2008-07-13 12:51   ` Mikko Husari
2008-07-13 11:32 ` Neil Bothwick
2008-07-13 12:50   ` Mikko Husari
2008-07-13 13:07     ` Neil Bothwick
2008-07-13 13:42       ` Mikko Husari

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=487929A2.1040806@husku.net \
    --to=husku@husku.net \
    --cc=gentoo-user@lists.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