Your message dated Sun, 22 Oct 2006 16:17:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line please add support for unionfs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: pbuilder
Version: 0.128
Severity: wishlist
Hi,
to quicken the way pbuilder works, I suggest an alternative to the usual
base.tgz-extracting, modifiying and directory deletion/base.tgz
recreating:
The base.tgz will be constantly extracted, i.e., a base-directory. All
operations that until now meant extracting, modifying, and recompression
will just work on that directory directly.
All other operations, especially package building, will take place in a
unionfs-mounted directoy in a way that a temporary writeable directory
is placed _above_ the base directy using unionfs, so that the programs
have the regular view of everything, but all and any modifications will
end up in the temporary directory. After the package was build, this
directory can erased as usual.
Advantages:
* Faster pbuilder upgrade (no .tgz handling)
* Faster package builds (no .tgz extracting, the directory to be
deleted is much smaller, as it only contains the changes)
* Less disk space usage while compiling (no base.tgz+build dir)
Disadvantages:
* More disk space usage while not working (base not compressed). Can be
amended by putting the base into a compressed partition, possible
using fuse.
The directory for the build modifications can even be on a ramdisk,
making the deletion a matter of no time, too.
Modifications to pbuilder should only affect a few clearly marked
places: Those that currently handle the .tgz and deletion of temporary
directories. Therefore, this feature can probably implemented by someone
other than the core developers. Of course it should be optional, and
migration should be possible (and is no problem) in both ways.
Thanks,
Joachim
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.otto
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages pbuilder depends on:
ii coreutils 5.2.1-2 The GNU core utilities
ii debianutils 2.14.1 Miscellaneous utilities specific t
ii debootstrap 0.3.1.4 Bootstrap a basic Debian system
ii gcc 4:4.0.0-2 The GNU C compiler
ii wget 1.10-3+1.10.1beta1 retrieves files from the web
Versions of packages pbuilder recommends:
ii devscripts 2.9.3 Scripts to make the life of a Debi
ii fakeroot 1.4.2 Gives a fake root environment
ii sudo 1.6.8p9-2 Provide limited super user privile
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Oct 22, 2006, Joachim Breitner wrote:
> I said “unionfs” because that's the only COW method I new back then. So
> if the cowdancer setup allows for fast operation in about the way I hope
> unionfs would help doing it, then from my side this bug has been
> resolved.
I think "fast" is too little to describe the new cowdancer support. I
am addicted now!
(Closing the bug.)
--
Loïc Minier <[EMAIL PROTECTED]>
--- End Message ---
