On Friday 21 January 2005 19:37, Stephen Quinney wrote: > Upon investigation I found that debian/rules is calling two scripts: > build-discover (which attempts to download the source for curl, expat > and discover) and build-paste (which attempts to grab the source for > coreutils). This is total and utter madness, I've never come across > anything so odd before in my experience of Debian packaging. There is absolutely _no_ reason to be rude about this. If you think that it is odd, then ok. But insulting me personally is unprofessional and certainly counterproductive. Just because it doesn't work like you would've done it is no indicator for "total and utter madness". <rant> It might have helped if you had asked for the reasons for this special construction, which I have not done just for the fun of it.... But I understand that flaming is easier, takes less of your seemingly valuable time and maybe gets you a few additional ego points then thinking about the issue and writing a constructive email with real suggestions for improving it. </rant> Btw, this is already documented in the changelog.
> You must not assume even the existence of a network connection from a > buildd never mind the ability to run apt-get. It must be possible to > build a package inside a self-contained chroot. You should also note > that there is a high chance that the apt source urls will not be > listed in typical chroots. In all of the build environments that I have access to, they are. I agree that some might not have this possibility, but then you could work with a local package mirror. > I am absolutely certain that you really do not need to download the > source code for each of these packages and then build them. There must > be a better way to achieve what you are trying to do here. OK, send me patches if you have a better solution. I will look at them and decide if they have other problems. In case you care about the reasoning for my decisions: it is all about maintainability and size: I do not want to: a) duplicate the complete sources in my package, because it would simply be a waste of space and bandwidth. b) extract only those source files that are really necessary and create a new build system for them, because that would mean a lot of effort for tracking upstream changes for no benefit (and for building the uclibc-linked discover binary, nearly all of the source files are necessary anyways). c) ship pre-compiled binaries in the source package, like it was done in the version before this "odd" construction. If you have a solution that does not need to download the source packages at build time (which is no problem for reasonable development environments) and does not have the problems listed above, then you are welcome to send me patches. I am not completely happy with the current solution and would like to do something about it. And since you are "absolutely certain" that there is such a solution, I am already delighted to get the chance to improve my package. PS: A second outright insulting email (aka. flame) will simply be ignored, because my time is also valuable. If you would like to resolve this in a constructive manner, then I am, as always, open to any suggestion. Rene
pgpjPqweqclrX.pgp
Description: PGP signature
