Greetings! Stephen Gran <[EMAIL PROTECTED]> writes:
> This one time, at band camp, Camm Maguire said: > > > also not up to a maintainer to decide that an architecture should not be > > > supported release wise... and if it would be there is a procedure to > > > > Not doing that, just saying I'm not going to adjust my packages for an > > arch which cannot provide the basic facility to package maintainers to > > support it. Human time is much more valuable than machine time, and > > having to spend months of the former pursuing the latter is just > > wrong. > > If you're unwilling to support your packages on multiple platforms, I > just don't know what to say. Perhaps you want to reconsider your I am quite willing if I can count on accessing a machine whenever a precious Debian development moment opens up. I've been with this project since the mid nineties, and I can assure you that I have spent *many* hours getting builds to run on rare platforms, including arm (take a look at axiom, for example, which required a by hand build of about one week.) I just believe that as a project, we have to realize that supporting architectures requires more than superhuman effort on the maintainer's part to find the few evanescent cycles as they may appear in random locations from time to time. > There are plenty of people who can provide access to arm machines to > you, and there are plenty of emulators availale if you can't be bothered > to find those people. Deciding that you don't care is really not an > option. Stephen, it is definitely not a question of not caring -- rather the opposite, the project is weakened if packages are ejected, and developer time wasted, pursuing the non-existent login. Believe me, I've tried. In years past, the type of approach you mention worked quite well. [EMAIL PROTECTED] was quite responsive in helping me outside the official Debian machine framework to get my packages going on arm. But now consider this: europa, elara -- still locked down from the breakin many months ago rameau, the old workhorse, gone smackdown, my old non-Debian standby, inaccessible agnesi, 'being setup' for many many months. I could once get into port 2260, but there was no chroot nor development env setup, now even that is locked down. Asked about this on debian-admin -- no reply leisner -- not up (yet?) asked on debian-arm for another box, a kind soul responded with an offer and requesting an ssh key, I replied, no reply, I replied again, no reply. This is just too hard. A large fraction of Debian development time winds up being simply trying to gain access, at least if situations like these prove to be the logjams. You have to ask yourself, if one really cares about Debian, what should the next step be? Upload the package with ! [ arm ], or let it sit with an rc bug for months waiting for a machine and risk missing the release deadline? These are literally the only choices in the absense of access. Now you do mention something I have not tried, and in fact still do not know if it provides an acceptable alternative -- emulators. Is the future for maintainers to upload binaries compiled under emulators? If so, I might be able to deal with this depending on the quality. What is the policy here? Can one upload arch-specific binary-only packages built under emulation? Take care, > -- > ----------------------------------------------------------------- > | ,''`. Stephen Gran | > | : :' : [EMAIL PROTECTED] | > | `. `' Debian user, admin, and developer | > | `- http://www.debian.org | > ----------------------------------------------------------------- -- Camm Maguire [EMAIL PROTECTED] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
