public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Canizo <conan@lugmen.org.ar>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] modifying locally an ebuild
Date: Wed, 31 Aug 2005 10:35:25 -0300	[thread overview]
Message-ID: <20050831133525.GB17307@lugmen.org.ar> (raw)
In-Reply-To: <431596D8.40805@planet.nl>

El 31/ago/2005 a las 08:39 -0300, Holly me decía:
> The probelm here is (likely) that the name of the package (for the
> purposes of the ebuild) is 'mutt-conan', not mutt.
> 
> The format for an overlay folder (like Portage) is
> 
> cat-egory/package-name/package-name.and-version.ebuild
> 
> so your ebuild should likely be in
> 
> /usr/local/portage/mail-client/mutt-conan/mutt-conan-1.5.8-r2.ebuild
> 
> rather than just 'mutt'.
> 
> I get caught by that one all the time

And i get caught even after reading this. But now i read a second time
and get that the *directory* where the ebuild remains *must* have the
same name as the package. I didn't pay attentio to this:
> /usr/local/portage/ ... /mutt-conan/ ...

But before realizing that i just changed the name back to *mutt* alone
and the command run sucessfull. So i decided to let that way since
emerge will tell from where comes the ebuild, as you say.

I can't wait to see this tested, i'm doing a sync right now and gonna
unfix mutt version in packages.mask so this afternoon will check what
happens when i try to 'emerge mutt' (surely gonna be a new version)

> Is this a behaviour that a significant portion of the mutt userbase
> might want? Or are you just weird ;) ?

Well, you use thunderbird, so maybe you're more like a "mouse user".
This is the thing: in mutt you can flag a message as important (you
got only one flag), also you have a 'ctrl-d' command that deletes a
full thread. Sometimes threads get off-topic (an unconstructive flame
for example) and when i realize that, and don't like the new topic i
just 'ctrl-d' them. But what if i've flagged some message? It means
that it's important to me, so i wanted to remain undeleted.  The
actual behaviour of mutt just delete everything.

That's what the patch provides me, and with a single line of code.
Simple. And David (the autor) do it so well that even added a new
option for it to be in '~/muttrc' and let the default to be the old
behaviour. So i think this patch can get to portage easily.

By the way, if anyone interested, this is it:
http://home.uchicago.edu/~dgc/sw/mutt/patch-1.5.8.dgc.flagsafe.1

> If you think it might be useful to other mutt
> users, submit it to b.g.o 

Doing this later.

> :) Yes, you can. Isn't Gentoo great? Did you know yesterday that "even
> you" could contribute to development? $DEITY, I *love* that.... !

Yeah! I think it's time to read Nagatoro link now.

-- 
Fernando Canizo - http://www.lugmen.org.ar/~conan/
#if 0
        linux-2.2.16/fs/buffer.c
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-08-31 13:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31  1:12 [gentoo-user] modifying locally an ebuild Fernando Canizo
2005-08-31  1:36 ` Holly Bostick
2005-08-31  3:23   ` Nick Rout
2005-08-31  5:56     ` Fernando Canizo
2005-08-31  6:37       ` Nick Rout
2005-08-31  7:34         ` Nagatoro
2005-08-31 13:15         ` Fernando Canizo
2005-08-31  5:42   ` Fernando Canizo
2005-08-31 11:39     ` Holly Bostick
2005-08-31 12:13       ` Neil Bothwick
2005-08-31 12:42         ` Holly Bostick
2005-08-31 13:31           ` Neil Bothwick
2005-08-31 14:06             ` Holly Bostick
2005-08-31 19:41               ` Neil Bothwick
2005-08-31 13:35       ` Fernando Canizo [this message]
2005-08-31 17:37         ` Holly Bostick
2005-09-01  5:37           ` [gentoo-user] " Moshe Kaminsky

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=20050831133525.GB17307@lugmen.org.ar \
    --to=conan@lugmen.org.ar \
    --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