El 31/ago/2005 a las 03:37 -0300, Nick me decía:
> no no, you put the epatch command in your ebuild file (your own version
> that you put in PORTAGE_OVERLAY.) Then the patch gets applied to the
> mutt source file before compilation.
Ah... Already did that! In my modified ebuild what i did was to copy
lines from other patches and then adecuate them.
> > I don't understand this either, if i put something un *my* portage
> > tree the mirrors get infested?
> >
>
> no. lets start again.
>
> there are two places that portage can get the patch from.
>
>
> 1. If it is small you can put it in ${FILESDIR} which is, in our case:
>
> /usr/local/portage/mail-client/mutt/files/cool-all-mutt.patch
>
> Then it is only on your system. If your revised ebuild gets accepted
> into portage then the patch file will also get in the portage tree and
> every gentooista will eventually get it via emerge sync.
>
> 2. If it is large, or if it is, for example, a commonly available public
> patch (for example that some third party has published) then you can
> instruct portage to download it from the net by specifying a SRC_URI,
> viz:
>
> SRC_URI="http://some.place.net/pub/patches/mutt/cool-all-mutt.patch";
>
>
> You can do that in your private OVERLAY ebuild, and as you say you found
> the patch on the net, that may be the best way to do it.
Cool, that's what i'll do.
> Again, if your revised ebuild gets accepted and if the "powers that be"
> get with it, the patch file might also get into the gentoo mirrors,
> meaning that it is easier to get with more redundancy.
I'm gonna try to file the bug report asking for it to be in portage
this afternoon. (got to go running now)
--
Fernando Canizo - http://www.lugmen.org.ar/~conan/
QOTD:
"I drive my car quietly, for it goes without saying."
--
gentoo-user@gentoo.org mailing list
