On Tue, May 12, 2015 at 02:22:15PM +0200, Lucas Nussbaum wrote: > Package: gem2deb > Version: 0.15 > Severity: wishlist > > 14:00 < lucas> terceiro: any objections to adding dh-make-ruby --refresh, > that moves away debian/, creates fresh content, merge the > changelog, and point to how to use meld to merge the rest > manually? > 14:02 < terceiro> lucas: I would copy (not move) debian/ away, and then > overwrite it's contents. This way you keep files that were > added by the maintainer but that dh-make-ruby would not > create otherwise > 14:03 < terceiro> make the merging easier IMO > 14:03 < terceiro> lucas: if debian/ exists, I think that coud even be the > default behavior > 14:03 < lucas> terceiro: I've tried both approaches. the problem with copying > is that you don't know if there are obsolete files around > 14:03 < terceiro> hm > 14:03 < lucas> meld + Copy to left / copy to right works better imho > 14:03 < lucas> in terms of workflow > 14:04 < terceiro> for me overwrite then `git diff` would work > 14:05 < lucas> I can see if it's easy to implement both > 14:05 < lucas> it probably is > 14:06 < terceiro> lucas: cool, I don't have a strong position though > 14:06 < terceiro> lucas: does making --refresh the default behavior when > debian/ already exists sound sane? > 14:07 < lucas> I think so, yes > 14:07 < terceiro> nice
I have just implement one half of this: a -w/--overwrite option that will, well, overwrite the files under debian/ that dh-make-ruby would have created if they didn't exist before. It seems that the other half (--refresh itself) should be easy, but I didn't get yet what's the idea. Should dh-make-ruby move debian/ away, recreate a fresh debian and then let the user use meld/whatever against them manually? -- Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
