Heads-up: brand new RPM version about to hit rawhide
Les Mikesell
lesmikesell at gmail.com
Tue Jul 15 16:41:55 UTC 2008
Dan Williams wrote:
>
> Yeah, there is actually a benefit to tarball+patches approach we take
> right now; and that benefit is that it's extremely easy to see just what
> we've done to the upstream package, and it's usually really easy to
> extract those changes and push them upstream.
Easier than working directly in a distributed SCM where you can see not
only the patch code but who committed it, when, and why? And how it
might differ from other distro-specific changes if they all end up in
the same repo...
> One problem working directly on exploded source trees is that you as a
> developer have to be much more disciplined to make small, targeted
> commits that are easily able to go upstream, otherwise you do end up
> with a huge diffmess that you simply can't upstream easily.
>
> And that's where we should always be working: upstream.
Likewise if they are using a distributed SCM, the best way to get
changes done there is to put the changes in a branch they can pull and
merge. The down side is going to be that there are several versions of
SCMs around and you'll have to follow the upstream conventions which
probably differ wildly, and figure out what to do with subversion.
--
Les Mikesell
lesmikesell at gmail.com
More information about the devel
mailing list