Re: m68k boot-floppies
> > boot-floppies can't be built on kullervo because it absolutely requires
> > root access, right?
> It requires root access (at least it did at home), but this does not mean it
> can not be built on kullervo. All packages being built, are built using
> sudo, which gives you root access. It just requires somebody who has the
> time, gaining root access is just an administrative (minor) problem, I would
> say.
At least. For your home machine, you can give yourself root or sudo
privileges all you like. For a remote machine, I'd be very cautious.
Part of the build doesn't require root access anyway. But that's a gripe
I have anyway with Debian builds: it's all or none, from make clean to
make binary. It would be tremendously helpful to have a separate hook from
dpkg-buildpackage to just package the whole stuff (starting with make
install) and another one to run without make clean, and stop short of make
install.
I have no time to first play with the configuration of the make variables,
then hack the makefile to work non destructive, then start the real work,
and finally back out all the convenience changes to the makefile again
before committing the real changes to CVS. Building boot floppies always
was a major PITA for me, second only to building dpkg devel versions. This
isn't just a porting job.
> Maybe the fixing of the boot-floppies can be done even without root access.
> It should not be a problem for Roman/You/me to start a build when things are
> fixed (in case Roman does not want more people to be root on that machine).
I have no sort of root access on that machine I know of. And I don't want
to have root access on kullervo anyway.
> > It requires unpacking m68k-support.tar.gz which is in the archive, then
> > some manual adaption of kernel packages names etc.
> Can't this be automated in the makefile?
Perhaps. But that's a bit beside the point - the tarball itself needs to
be maintained some way or other (i.e. the Amiga booter scripts, the
install guides, the Mac booter apps and stuff). The whole freaking build
of the Mac install kit as StuffIt archive can't be automated at all before
someone writes a StuffIt packer for Linux. The whole generation of the
.map files and install scripts for the CD and the FTP archive isn't
automated. Maybe the powerpc port comes up with a good way to do that,
they seem to have the same problem with entirely different subarchs.
In a nutshell, this sucks.
Michael
Reply to: