I think I misunderstood your intent -- thought you were going to merge your whole build/mrvn tree back to build in 12 hours. I see now that you only mean to change build/debian, which I have no problem with since build/debian is not in a releasable state on the mainline at all right now. You can merge it right now as far as I'm concerned. Goswin von Brederlow wrote: > > The build daemons have an extensive, and easy to use logging system. > > There is no need to reinvent this wheel either. > > I guess I can attach all the diskusage-* files to the buildlog by > cating them at the end. Not as easy to look through but I can write a > small script to fetch the last buildlog and present the information > nicely. It will be no worse then the build logs of many packages in debian and I don't anticipate any trouble using a single log when autobuilding fails to track down the problem. > But then what do I put into the deb? Just changelog and copyright? > The main purpose of the buildlog package will be to trigger the build > of images and add them to the changes file (if the ftpmaster agrees). > > If the debian-cd maintainer wants a debian-installer-bootimages.deb > instead of fetching the images from net or a mirror that package can > take over image generation. > > Point is that we need one dummy (u)deb to trigger the build at the > moment and just throwing the build log and status files together > seemed to be the least work wasted. I don't know. -- see shy jo
Attachment:
signature.asc
Description: Digital signature