On Thursday 26 April 2001 15:44, Ben Burton wrote: > > As for potato packages, I'm not sure how those are generally done. If all > else fails, I can ask for use of the machine I was last building potato > packages on, although I will need to check first because they're big and > nasty and take three hours to compile on my laptop and almost blow my > physical+swap memory limits, so I don't want to just log on to someone > else's box and hit build without asking. :) >
I'll speak for Ivan... The "normal" process for KDE Debian potato packages has been for Ivan to take the ones he has packaged for sid and modify them appropriately for potato. When he finishes that process, he typically build i386 and sparc packages. I build powerpc packages. All of these, including source, then wind up on kde.debian.net. The last two koffice packages prior to the "version switch", I grabbed the sid source, "downgraded" any debian/control and debian/rules things required to get it to build on potato, and then built source, i386 and powerpc packages. The first "version switched" koffice package, I attempted to do the same thing. I ended up with strange things like each package having all the manpages, some missing library dependencies, and maybe some other things. Ivan then "took a look at it" and (I think) created the current i386 packages on kde.debian.net. Ben, if you want to make a potato source package, I will build the i386 and powerpc packages for kde.debian.net. I am also willing to keep doing the "downgrade" debian/control and debian/rules approach of creating a potato package from the sid (or woody when it gets there) source package. Rick -- [EMAIL PROTECTED]
