[Joerg Mayer <jmayer@xxxxxxxxx>]

On Mon, Aug 15, 2005 at 10:26:48AM -0700, Guy Harris wrote:
...

OK to everything above.

> 	4) a patch adds a useful feature not in the current version of the 
> software, in which case it should be applied (although we might have to 
> generalize it so that it works on other platforms, or at least doesn't 
> break things on those platforms).

I disagree here. If a patch is too specific or it would just make the code
too hard to read but is still of interest to some users we may privide it
as a patch inside the repository.
An example for a patch that is too specific: The categories field in ethereal.desktop.
If we want to provide packages that fit properly into different distributions,
then we need to change this according to the distribution.
An example for a patch that might better remain a separate patch is the
capabilities patch (but then again, that's just my personal opinion because
I understand too little of capabilities).
With Suse, there are distro specific build process patches (mostly path
changes) that should be picked up if we wanted to build proper Suse packages.

 ciao
     Joerg


-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.