Re: gem2deb + gbp workflow
Gioele,
* Gioele Barabucci <gioele@svario.it> [131004 07:27]:
> [..] I read this as "Do not amend the
> first commit created using the gem2deb". What is the point of this
> suggestion? The packages created by gem2deb are very rudimentary and
> just plain wrong on many accounts (for example the debian/copyright
> files). The only interesting value I see here is to track changes so
> one can see what gem2deb got wrong and automate this in another
> release. But wouldn't that be better served by simple bug reports?
The interesting bits are the work of humans, not the work of a
conversion script.
As gem2deb evolves, it's behaviour can change -- therefore, in the
future it may be interesting to see if a particular thing was a
decision made by the human packager, or by gem2deb.
> Another thing I do not understand is the fact that the packages
> produced by gem2deb are supposed to Build-Depend on gem2deb itself.
> How come the dh-ruby subsystem is not separated from gem2deb (that I
> thought was just a simple conversion script)?
The gem2deb package is 44K in size; there's no point in splitting
it for size reasons; there's no point in splitting them for
functionality reasons (i.e. gem2deb can be installed on any host).
HTH,
--
Christian Hofstaedtler | design, deploy, scale
http://christian.hofstaedtler.name/ | phone +43 720 699846
Reply to: