Thorsten Glaser wrote:
And what if one single file is patched for different reasons?
Then the OLD system definitively sucks more than update-patches,
because if a file is patched several times, stuff like "which
.orig file belongs to which patch and which is my real pristine
file now", "which patch depends on which patch", etc. appears.
This point of yours seems to be the weak point of update-patches
at first, but if you work with it for a while, you see it's
actually an improvement. Plus, you always get diffs which are
guaranteed to apply. They're even applying with a greater chance
to succeed after you update the package. (You should still regen
them afterwards, but it helps the upgrader.)
Sure, this makes it easier for you guys to throw in changes, because you
don't have to care about structuring them properly. But what about
people not involved in your project that may want to review your
patches? IMHO as the size and number of the patches grow, it becomes a
nightmare trying to figure out which patch chunk belongs to which
logical change.
Or is this not something that you think you should care about?
- Felix
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
