Reply to message «Re: Can not apply patch 7.3.202, 203, 223 cleanly», sent 20:01:48 22 June 2011, Wednesday by Christian J. Robinson:
> I can't speak for Ben, but for me it's because that would break the > self-contained source RPM package I roll for my CentOS machines. Self-contained? What is the problem with moving output of hg diff to this package and why you mess up with using patches at all and don't just put snapshot of repository at given revision? I can understand the need of patches for ebuilds, but for rpm packages... Ebuilds though don't download them from official location (maybe because of such problems), so it does not matter either. Original message: > On Tue, 21 Jun 2011, ZyX wrote: > > Reply to message «Re: Can not apply patch 7.3.202, 203, 223 cleanly», > > sent 18:37:42 21 June 2011, Tuesday > > by Ben Fritz: > > > > Why you can't just use mercurial repository? > > I can't speak for Ben, but for me it's because that would break the > self-contained source RPM package I roll for my CentOS machines. This > applies to virtually all RPM based Linux distributions, and > conceivably also Debian based, and other systems that use a similar > concept. > > While it's not /impossible/ to integrate mercurial into source RPM > build scripts, it is definitely considered a no-no. > > Not to be "snippy," but why put out patches in the first place if > they're just broken? > > - Christian
signature.asc
Description: This is a digitally signed message part.
