public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Some 'proper coding' notes for ebuilds
Date: Sat, 2 Aug 2003 23:04:51 -0400	[thread overview]
Message-ID: <200308022304.51692.vapier@gentoo.org> (raw)
In-Reply-To: <3F2C7887.50103@gentoo.org>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 812 bytes --]

On Saturday 02 August 2003 22:50, Kumba wrote:
> Isn't the only time we want to avoid this on a kernel ebuild?  There was
> an email many weeks ago on -dev I think (mighta been -core) which said
> to avoid using epatch on kernel sources, due to it's brute-force method.
>   Also, what about "xpatch"?  I had heard of this mechanism used awhile
> ago, but not recently.

this was meant as a general heads up ... i'm sure the kernel team can handle 
the kernel ebuilds just fine themselves ;)

as for xpatch, i havent utilized it myself and havent looked into it ... right 
now 'epatch' is in portage, 'xpatch' is not ... it doesnt really matter too 
much since if we upgrade all packages to use epatch, we can easily switch 
over to 'xpatch'

pkgs that currently use xpatch:
app-text/a2ps
-mike

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2003-08-03  3:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  2:29 [gentoo-dev] Some 'proper coding' notes for ebuilds Mike Frysinger
2003-08-03  2:34 ` Mike Frysinger
2003-08-03  2:38   ` Mike Frysinger
2003-08-03  2:50     ` Kumba
2003-08-03  3:04       ` Mike Frysinger [this message]
2003-08-03 15:23         ` Martin Schlemmer
2003-08-03 18:44           ` Mike Frysinger
2003-08-03 15:10     ` Mamoru KOMACHI
2003-08-03 15:40       ` Paul de Vrieze
2003-08-03 16:23         ` Mamoru KOMACHI
2003-08-03 16:27       ` Georgi Georgiev
2003-08-03 17:04         ` Mamoru KOMACHI
2003-08-03 15:30     ` Martin Schlemmer
2003-08-11 13:45     ` Patrick Kursawe
2003-08-11 14:58       ` Mike Frysinger
2003-08-03  5:31   ` Jason A. Mobarak
2003-08-03  4:56     ` Mike Frysinger
2003-08-03  6:11     ` Luke-Jr
2003-08-03 14:55   ` Stuart Herbert
2003-08-03 15:18     ` Martin Schlemmer
2003-08-03 18:07       ` Stuart Herbert
2003-08-03 18:48         ` Mike Frysinger
2003-08-03 18:53           ` Stuart Herbert
2003-08-03 20:27             ` George Shapovalov
2003-08-03 20:34               ` Stuart Herbert
2003-08-03 22:15                 ` George Shapovalov
2003-08-03 22:56                   ` Don Seiler
2003-08-08 15:21                     ` Anthony de Boer
2003-08-08 15:33                       ` Marius Mauch
2003-08-08 18:25                       ` George Shapovalov
2003-08-08 19:16                         ` Douglas Russell
2003-08-08 20:12                           ` George Shapovalov
2003-08-08 23:01                             ` Mike Frysinger
2003-08-10  2:58                             ` George Shapovalov
2003-08-03 22:19                 ` Aron Griffis
     [not found]             ` <20030803223541.05d10e90.spider@gentoo.org>
2003-08-03 20:43               ` Stuart Herbert

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=200308022304.51692.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@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