On Mon, Jun 30, 2008 at 08:18:41PM +0100, Andrew Flegg wrote: > On Mon, Jun 30, 2008 at 8:11 PM, Marius Gedminas <[EMAIL PROTECTED]> wrote: > > On Mon, Jun 30, 2008 at 08:08:37PM +0100, Andrew Flegg wrote: > >> > >> https://garage.maemo.org/builder/diablo/vim_7.0/sources/ > > > > It looks like a native Debian package (i.e. the debian/ thing is inside > > the tarball). How hard would it be to get mud-builder produce > > non-native Debian packages (i.e. .orig.tar.gz + .diff.gz + .dsc)? > > It /should/ be relatively trivial. I'm not sure, OTTOMH, whether it'd > need any cleverness to handle upstream Debian sources which will > already have a .diff.gz and then may have further Maemo patches.
Hm. This is slowly drifting into the "let's just use a Distributed Version Control System" territory. > Apart from being slightly more consistent with "the Debian way", I > suppose the key advantage is that it's potentially easier for someone > to try and apply the .diff.gz to a different upstream source if the > original maintainer gets hit by a bus? Or is just busy/on vacation. I also think that having a Maemo diff would make porting to new Maemo versions easier: you get to see all the places that needed Maemo-specific modifications. Hm. Suddenly I'm not sure there are any advantages over just trying to rebuild the already-patched source tree, and fixing errors on the go. > Any other reason I'm missing? The other reason (at least for Debian) is that when you fix packaging bugs, you only need to upload the .diff.gz and therefore save bandwidth. I don't know if this is currently applicable to Maemo, but if supported, it would help people with low bandwidth trying to debug package build problems on the autobuilder. Marius Gedminas -- To err is human, but to really foul things up requires a computer.
signature.asc
Description: Digital signature
_______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
