Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
Hi, Junichi Uekawa wrote: > > pbuilder takes somewhat different approach in that it keeps > tar.gz of chroot images, and extracting it whenever a new build starts. > This is advantageous in that it is possible to have the cleanest possible > environment (in a way), and also allows for concurrent build process > (for those people who are inpatient). Ok. The package has a script, checkroot, to see if the chroot contents differ from a reference. It won't, as sbuild is used here, unless the user installs a package manually. It's very cool having permanent chroots if you have the space. You really have a totally separate install -- maybe stable where you run unstable in base. You can go into it and use it as you would a normal install. But I agree that sbuild and pbuilder take a different approach. I'll plug away. I expect to upload it in a couple days and fix any chroot building quirks later. Rick
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
On Wed, 21 Nov 2001 12:45:14 -0800 Rick Younie <[EMAIL PROTECTED]> wrote: I don't know if I've replied to this message, but trying again. > The sbuild package chroot creation sucks and I don't know when > I'll get to improving it -- poor net connection currently and > it's not very interesting. :-) You set up the chroots once > and then just keep them current from then on. pbuilder takes somewhat different approach in that it keeps tar.gz of chroot images, and extracting it whenever a new build starts. This is advantageous in that it is possible to have the cleanest possible environment (in a way), and also allows for concurrent build process (for those people who are inpatient). > It might make sense to add sbuild to your package, maybe as an > alternate build method. I haven't checked out out pbuilder yet > so I don't know if this make sense. I'll grab it right now. pbuilder-buildpackage may be able to use sbuild instead of its own build engine. > There's currently a little fork with the sbuild in most common > use and CVS. If you want to combine the two packages, I could > co-maintain until this settles down; or not? I would rather not maintain sbuild. I would rather keep sbuild out of pbuilder, as a separate package, because the upstream is quite different. My impression is that sbuild is out in the wild in many different forms and forks... regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
James Troup wrote: > Rick Younie <[EMAIL PROTECTED]> writes: > > The sbuild package chroot creation sucks > > So use debootstrap and buildd.chroot[1] then. It would only takes > about 5 commands more and you could ditch buildd-setup-chroot > entirely. buildd-setup-chroot requires a local archive, no? I've never used it. I included a script and some instructions on building pot./sid chroots starting with the base2.2 tarball, copying, dist-upgrading. Sucks hard, but I know it works. I had some problems with debootstrap in the past (haven't looked recently) so I thought I'd wait a while before using it here. Didn't know about buildd.chroot. > > > It might make sense to add sbuild to your package, > > Err, I really don't think so. But hey, it's your time. Which is why I tried to push it on Junichi.:-) I don't really need another package. The sbuild stuff is simple because my nose is in it every day but the chroot side is a PITA. But you've convinced me (I'm easy). I won't have a decent machine for a couple weeks. I'll check out buildd.chroot and debootstrap then. > > > There's currently a little fork with the sbuild in most common use > > and CVS. > > Err, no there's not? apt patches got merged... I packaged the sbuild with the patch Ryan posted to -disc. CVS still has the FetchFile stuff as fallback. My understanding is that would be removed if it works OK over the next few weeks. Rick --
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
Rick Younie <[EMAIL PROTECTED]> writes: > Adding -devel; trying to get some feedback before uploading. It's > only at the works for me stage. Removing -devel, because it bores me. > The sbuild package chroot creation sucks So use debootstrap and buildd.chroot[1] then. It would only takes about 5 commands more and you could ditch buildd-setup-chroot entirely. > It might make sense to add sbuild to your package, Err, I really don't think so. But hey, it's your time. > There's currently a little fork with the sbuild in most common use > and CVS. Err, no there's not? apt patches got merged... > If you want to combine the two packages, I could co-maintain until > this settles down; or not? IMNSHO pbuilder is a red herring; if you're going to package sbuild feel free, but I think any kind of chimera hybrid with pbuilder is ill advised at best. YMMV. -- James [1] auric:~rmurray/buildd.chroot
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
Adding -devel; trying to get some feedback before uploading. It's only at the works for me stage. Junichi Uekawa wrote: > > > If you can use/adapt any of the scripts, feel free. I'll have a > > look at pbuilder and see if there's anything I can steal. :-) > > You can probably get pbuilder to do the debootstrap creation. > That's the part pbuilder seems to do best. > > Other parts are not much of interest, I think. > Both of them are small applications. > > Making pbuilder to use sbuild instead of pbuilder-buildpackage for > building and build-dep checking might be an interesting challenge. The sbuild package chroot creation sucks and I don't know when I'll get to improving it -- poor net connection currently and it's not very interesting. :-) You set up the chroots once and then just keep them current from then on. It might make sense to add sbuild to your package, maybe as an alternate build method. I haven't checked out out pbuilder yet so I don't know if this make sense. I'll grab it right now. There's currently a little fork with the sbuild in most common use and CVS. If you want to combine the two packages, I could co-maintain until this settles down; or not? Rick --
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
Junichi Uekawa wrote: > On Mon, 19 Nov 2001 17:00:50 -0800 > Rick Younie <[EMAIL PROTECTED]> wrote: > > Hi, > > > A first cut is at http://klecker.debian.org/~younie/sbuild/ . > > Feedback most welcome. > > It's very nice that you are trying to make a package of what > has not been packaged, and has been very much wanted. > > > # yes, and I admit having given up packaging this > program. Instead, wrote my own. Hi, I understand pbuilder works very well. There were some debootstrap problems initially when I tried it and then my broadband connection went away. I'd packaged buildd/sbuild (sort of) for my own use for checking out m68k build failures so I thought I'd ITP sbuild. If wanna-build gets packaged, this package will probably go away. If you can use/adapt any of the scripts, feel free. I'll have a look at pbuilder and see if there's anything I can steal. :-) Rick --
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
On Tue, 20 Nov 2001 11:59:29 -0800 Rick Younie <[EMAIL PROTECTED]> wrote: Hi, > I understand pbuilder works very well. There were some > debootstrap problems initially when I tried it and then my > broadband connection went away. Oh. okay. It still requires about 100MB of download for initial setup, which may be not nice for many users. It should be possible to start up from CD-Rom... > I'd packaged buildd/sbuild (sort of) for my own use for checking > out m68k build failures so I thought I'd ITP sbuild. If > wanna-build gets packaged, this package will probably go away. Hmm... Okay. I was hoping to get the mail interface of wanna-build to interface with pbuilder somehow, but not got to it yet. > If you can use/adapt any of the scripts, feel free. I'll have a > look at pbuilder and see if there's anything I can steal. :-) You can probably get pbuilder to do the debootstrap creation. That's the part pbuilder seems to do best. Other parts are not much of interest, I think. Both of them are small applications. Making pbuilder to use sbuild instead of pbuilder-buildpackage for building and build-dep checking might be an interesting challenge. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
On Mon, 19 Nov 2001 17:00:50 -0800 Rick Younie <[EMAIL PROTECTED]> wrote: Hi, > A first cut is at http://klecker.debian.org/~younie/sbuild/ . > Feedback most welcome. It's very nice that you are trying to make a package of what has not been packaged, and has been very much wanted. # yes, and I admit having given up packaging this program. Instead, wrote my own. -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Bug#120309: ITP: sbuild -- Tool for building Debian binary packages from Debian sources
Package: wnpp Version: N/A; reported 2001-11-19 Severity: wishlist * Package name: sbuild Version : 0.1 Upstream Author : Roman Hodek * URL : http://klecker.debian.org/~younie/sbuild/ * License : GPL Description : Tool for building Debian binary packages from Debian sources sbuild builds binary packages from source. It can do its work in chroots so both stable and unstable environments can be used on the same machine. It's also useful for figuring out a package's build dependencies. sbuild is part of the wanna-build build system used by most architectures to build packages for Debian. A first cut is at http://klecker.debian.org/~younie/sbuild/ . Feedback most welcome.
