[pacman-dev] bzip2 package compression
I changed these in /etc/makepkg.conf to bz2 variants ages ago and assumed that the resulting packages would be bzip2 compressed. When I double checked the packages they were still only gzip compressed even though the extension was tar.bz2. Everything works so I didn't pick it up but I'd be interested in the bandwidth saving from bzip2 compression. PKGEXT='.pkg.tar.bz2' SRCEXT='.src.tar.bz2' DB_COMPRESSION='bz2' Is there a reason that a -cjf is not used in makepkg ? % grep bsdtar /usr/bin/makepkg cmd="bsdtar -x -f $file" ;; if ! bsdtar -czf "$pkg_file" $comp_files *; then bsdtar -xOf "$old_file" .PKGINFO > "$pkginfo" || continue if ! bsdtar -czLf "$pkg_file" ${pkgname}; then --markc
On Sat, Dec 6, 2008 at 9:04 AM, Mark Constable <markc@renta.net> wrote:
I changed these in /etc/makepkg.conf to bz2 variants ages ago and assumed that the resulting packages would be bzip2 compressed. When I double checked the packages they were still only gzip compressed even though the extension was tar.bz2. Everything works so I didn't pick it up but I'd be interested in the bandwidth saving from bzip2 compression.
PKGEXT='.pkg.tar.bz2' SRCEXT='.src.tar.bz2' DB_COMPRESSION='bz2'
Is there a reason that a -cjf is not used in makepkg ?
local TAR_OPT case "$PKGEXT" in *tar.gz) TAR_OPT="z" ;; *tar.bz2) TAR_OPT="j" ;; *) warning "$(gettext "'%s' is not a valid archive extension.")" \ "$PKGEXT" ;; esac The current code is a bit smarter and compresses correctly depending on the extension. -Dan
On 2008-12-07, Dan McGee wrote:
Is there a reason that a -cjf is not used in makepkg ? ... The current code is a bit smarter and compresses correctly depending on the extension.
Ah cool, I presume this is in your Git repo? If so, do you think your current git repo is "stable enough" to give this a whirl with the few dozen folks using the daily kde-svn packages? --markc
On Sat, Dec 6, 2008 at 8:29 PM, Mark Constable <markc@renta.net> wrote:
On 2008-12-07, Dan McGee wrote:
Is there a reason that a -cjf is not used in makepkg ? ... The current code is a bit smarter and compresses correctly depending on the extension.
Ah cool, I presume this is in your Git repo?
If so, do you think your current git repo is "stable enough" to give this a whirl with the few dozen folks using the daily kde-svn packages?
Yeah this has probably been in GIT for some time. All of us that are regular contributors to pacman are already using pacman-git, so yeah, it better be stable. If you do go this route, be sure to report problems to the list or in Flyspray (set the reported version to 'git'). -Dan
participants (2)
-
Dan McGee
-
Mark Constable