|
On Wednesday, April 18, 2012 10:49:34 AM Scott Kitterman wrote: > Alternately you could invest a little time in understanding what Barry's > written up and build both sets of binaries from one source. This is the > usual method. The problem is not understanding. It is a problem of style. Let us take one snippet > python$* setup.py install --root=$(CURDIR)/debian/tmp > --install-layout=deb That is the usual way we install in March 2012. But "the usual way we install" is a moving target; It will change. I don't want to codify "the usual way we install" in March 2012 and then maintain that moving target as it moves. I want to write code that means "install in the usual way" and let the code that implements that concept be maintained by someone smarter than me. It is not good design to have a bunch moving targets all tracked by multiple packagers with various abilities and attention spans. This is not criticism of Barry; He has written excellent documentation on how to join the cargo cult. I am saying that we ought to find ways of not joining cargo cults. It is not about me or my level of understanding. Every line of code I write has to be maintained by somebody. Eventually, by somebody other than me; I am not going to live forever. Therefore, I resist writting lines of code. > A separate source package doesn't make it any easier as it > would still have to build for python3. When I build for python2 alone I don't have to override dh_auto_build or dh_auto_install. I assume the same would be true if building for python3 alone. It is only when I want both in the same source package that I need these complicated overrides that create moving targets. > > Scott K -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117 |
Attachment:
signature.asc
Description: This is a digitally signed message part.