* Stéphane Glondu <st...@glondu.net> [090525 10:39]: > You sound like you are developing "complex" features in your Debian > packages, features that might be concurrently developped inside a > packaging team. This doesn't sound right for me. I never do such complex > development inside a package. Most of the time, patches are just fixes > to make the upstream package more Debian-friendly, or patches taken from > upstream's VCS. But maybe I don't maintain "real-life" packages...
> Don't be mistaken: I don't say that packagers must not work on upstream > features; I just say they shouldn't do it as part of their Debian packaging. I've seen these discussions about "developping" in package too, and been puzzled... I thought "upstream" was where *development* was intended to happen... Sure, now that the world has DVCS, "upstream" doesn't have be the "canonoical" upstream, but I'm not putting complex patches into my "Debian package", I'm using a "different" upstream tarball, all the development compilications/interactions/dependancies are all in my "upstream" git repository, and which ever "version" I build the orig.tar.gz for has all that information in it's history/DAG... Why are all these new features *not* being developped upstream? Remember, in the DVCS world, upstream is no longer limited to "ftp.somewhere.com/pub/software-$VERSION.tar.gz"... Am I just too simple? a. -- Aidan Van Dyk Create like a god, ai...@highrise.ca command like a king, http://www.highrise.ca/ work like a slave.
signature.asc
Description: Digital signature
_______________________________________________ vcs-pkg-discuss mailing list vcs-pkg-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/vcs-pkg-discuss
