Re: [Gnumed-devel] restrictions vs. conventions (uncertain date-time)

[Karsten Hilbert]

On Sat, Aug 24, 2013 at 03:38:53PM +0000, Jim Busser wrote:

> Assuming that I would not want to evolve 'away' from "GNUmed main" any more 
> than necessary, then some way to track along side it would seem necessary for 
> sanity.
> 
> I would imagine that starting with "GNUmed main" and then identifying the 
> things desired to customize and making those changes,
> and then experiencing all unwanted side effects, and then fixing those 
> side-effects, is fine until wanting to enjoy something new available in 
> "GNUmed main".
> 
> Are the two basic approaches to doing this
> 
> (1) taking "the new GNUmed release" and re-applying -- to the extent that one 
> can -- all of one's own patches and detecting and fixing new 
> incompatibilities with new local patches, or alternatively
> 
> (2) taking one's "fork", and then applying to it all the patches which had in 
> the meantime been applied to "GNUmed main" in order for it to become "new 
> GNUmed release"
> 
> and where maintaining (2) is more complex and requires a higher level of 
> skills to keep working than (1)?

The idea would be to feed those patches back into main such
as to make the fork disappear as much as possible.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346