Your message dated Fri, 17 Nov 2006 22:02:10 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#392435: fixed in ccache 2.4-7
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: ccache

I recently wrote this script to help manage the ccache symbolic links the I was 
previously creating by hand in /usr/local/bin.

Just in case it is useful to others I thought I would submit it for potential 
inclusion in the ccache debian package.

Thanks.

------- SNIP -------
#!/bin/sh
#
# Update compiler links to ccache (in /usr/local/bin)
#
# The idea is that /usr/local/bin is ahead of /usr/bin in your PATH, so adding
# the link /usr/local/bin/cc -> /usr/bin/ccache means that it is run instead of
# /usr/bin/cc
#
# Written by: Behan Webster <[EMAIL PROTECTED]>
#

DIRECTORY=/usr/local/bin
CCACHE=/usr/bin/ccache
CCDIR=/usr/lib/ccache

usage() {
    echo "Usage: `basename $0` [--directory <dir>] [--remove]"
    exit 0
}

while [ $# -gt 0 ] ; do
    case "$1" in
        -d*|--d*|--directory) DIRECTORY=$2; shift; shift;;
        -h*|--h*|--help) usage;;
        -r*|--r*|--remove) REMOVE=1; shift;;
        -t*|--t*|--test) TEST=echo; shift;;
    esac
done

for FILE in `cd $CCDIR; ls` ; do
    LINK=$DIRECTORY/$FILE
    if [ -z "$REMOVE" ] ; then
        # Add link
        $TEST ln -fs $CCACHE $LINK
    else
        # Remove link
        if [ -L "$LINK" ] ; then
            $TEST rm -f $LINK
        fi
    fi
done

# vim: sw=4 ts=4
------- SNIP -------


-- 
Behan Webster
[EMAIL PROTECTED]



--- End Message ---
--- Begin Message ---
Source: ccache
Source-Version: 2.4-7

We believe that the bug you reported is fixed in the latest version of
ccache, which is due to be installed in the Debian FTP archive:

ccache_2.4-7.diff.gz
  to pool/main/c/ccache/ccache_2.4-7.diff.gz
ccache_2.4-7.dsc
  to pool/main/c/ccache/ccache_2.4-7.dsc
ccache_2.4-7_amd64.deb
  to pool/main/c/ccache/ccache_2.4-7_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francois Marier <[EMAIL PROTECTED]> (supplier of updated ccache package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 18 Nov 2006 00:50:59 -0500
Source: ccache
Binary: ccache
Architecture: source amd64
Version: 2.4-7
Distribution: unstable
Urgency: low
Maintainer: Francois Marier <[EMAIL PROTECTED]>
Changed-By: Francois Marier <[EMAIL PROTECTED]>
Description: 
 ccache     - Compiler results cacher, for fast recompiles
Closes: 297126 392435 396350
Changes: 
 ccache (2.4-7) unstable; urgency=low
 .
   * Use the real compiler when HOME is not set (closes: #396350)
   * Include user script under doc/examples (closes: #392435)
     Thanks to Behan Webster!
   * Add support for GNU --long options (closes: #297126)
Files: 
 b4f15d64ff038a1509082ffdec82d41d 566 devel optional ccache_2.4-7.dsc
 0d1d9c58c695ed3123a6810aa9713f6e 28398 devel optional ccache_2.4-7.diff.gz
 1206f1e4f8cac2f63428f4b408b57393 30218 devel optional ccache_2.4-7_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFXqBSScUZKBnQNIYRAgOzAJ4mvJn4EHl9KO45Awe67EMgMjSnDwCgjany
ghDl8pT7dzxXIjFpZsUVIgA=
=nczk
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to