On Wed, Mar 17, 2004 at 11:05:32AM -0600, Adam Heath wrote: > Debian packages are, by far and large, a combination of external source > archives, and various patches. These patches can be further sub-divided into > debian-specific(both new features and fixes), and upstream changes(ones > imported from upstream, or not yet sent upstream). > > As package development progresses, these changes: > > * get ported to newer upstreams > * get reimplemented > * get broken/fixed > > All these modifications to these changes don't all happen at once, and several > changesets can even be modified in parallel. > > As these changesets get modified, it's best to keep each discreet change > separate, and not all mingled into one, so that > removing/exporting/forward-porting is easier to do. This is the sort of problem that arch was designed to solve. Specifically it's the prism merge technique. Here's one description of it: http://mail.gnu.org/archive/html/gnu-arch-users/2003-09/msg01654.html Here's one of it being applied to Debian packages, complete with links to packages being maintained that way: http://arch.debian.org/arch/private/srivasta/ -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- |
Attachment:
signature.asc
Description: Digital signature