Frank Küster <[email protected]> writes:
> George Danchev <[email protected]> wrote:
>
>>> > But you lose debian specific patches to be clearly separated from the
>>> > upstrem source (digging diff.gz for that is not fun), unless one knows
>>> > where to find
>>>
>>> First, what is a "Debian-specific patch?" Isn't everything in diff.gz
>>> that?
>>
>> Right, but you have parts which touch upstream files (debian/patches/*), and
>> parts which does not (debian/!patches). I prefer them to be clearly separated
>> when the whole debian source package is unpacked.
>
> Not only that. Many packages make changes to upstream files that are
> Debian-specific (e.g. for using infrastructure or libraries that don't
> exist outside), but also changes to upstream files that will/should be
> temporary because upstream will apply the same patch, has been asked to,
> or the patch has been taken from their development version.
Iff we use a branch to each change we can have same behaviour using a
SCM but anyone that would want to change or contrib changes will need
to learn how we deal with this all.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [email protected] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
you the whole house."