Re: [gentoo-dev] ebuild policy questions.

["Tod M. Neidt" <tod@gentoo.org>]

Hi Terje!

I should have explicitly discussed the distinction between upstream and
third-party patches and those that are specific to Gentoo Linux.  I
assumed that we were talking about the former in my previous post.

Normally gentoo specific patches created by the ebuild author are kept
in the files directory.  A suffix of "-gentoo" is typically appended to
indicate this.  For example, xgammon-0.98-gentoo-makefile.patch, or
something to that effect.

Sorry for any confusion that this may have caused.

Regards,

tod

On Fri, 2002-04-12 at 05:27, Terje Kvernes wrote:



> > For patch files (especially large ones) include the URL to the patch
> > in the SRC_URI string so that it will be downloaded with the source
> > tarball and stored in ${DISTDIR}, i.e. /usr/portage/distfiles by
> > default.  See the dev-lang/python ebuild for a good example (In fact
> > the python ebuild is a good example for a variety ebuild techniques
> > for uncommon situations)
> 
>   hm.  the patches I need total about 1K, and I _could_ host the
>   patches via http.
>  
> > If the patch files are small (working definition of small not much
> > larger than the ebuild itself), placing them in the files directory
> > is ok, but the former method is prefereable.
> 
>   okay, I'll try getting them to work via http.  <pause for half an
>   hour>.  okay, done.  :)  now just to check that things work and
>   submit.  should I attach the patches as well?
>  
>