There is still a persistent daemon running after 1st HPLIP usage (hpssd),
but it is not a startup daemon. We are working on changing the architecture
to remove it as well.

Thanks for supporting HPLIP with the Slackware package.

-Don


On 6/30/07, Richard David Sherman <[EMAIL PROTECTED]> wrote:

Using the bash script shown below I have created a Slackware
Package for the latest version of hplip. (This script has
been used for several years with each new release of hplip &
hpoj before the project name change, modified appropriately.)


#!/bin/bash
#2007JUN29
NAME=hplip
V=2.7.6
SRCNAME=$NAME-$V.tar.gz
PKGNAME=$NAME-$V-i686-rds.tgz
BUILD=$TMPDIR/$NAME-$V
PKG=$BUILD/slack
DEV0=/dev/null
Build()
    {
    if      [[ ! -e $SRCNAME ]]
    then    echo Fetch $SRCNAME ; setterm -cursor on ; exit
    fi
    echo Extract ; rm -fr $BUILD ; tar -xzf $SRCNAME ; cd $BUILD
    echo Configure
    ./configure --disable-network-build --disable-pp-build \
                --disable-gui-build --disable-foomatic-xml-install \
                --disable-doc-build --enable-foomatic-ppd-install \
                --prefix=/usr &>configureLog
    echo Build ; make &>$DEV0
    echo Install ; mkdir $PKG ; make install DESTDIR=$PKG &>$DEV0
    }
Package()
    {
    if      [[ ! -d $BUILD ]]
    then    echo $BUILD does NOT exist ; setterm -cursor on ; exit
    else    cd $BUILD
    fi
    echo Package ; cd $PKG
    makepkg -l y -c n $TMPDIR/$PKGNAME &>$DEV0
    }
cd $TMPDIR ; setterm -cursor off ; clear
Build
Package
echo Done ; setterm -cursor on
#/.hplip ... why?


It builds, installs, & functions flawlessly!

But, on rebooting the system, it places a spurious /.hplip directory
containing an empty hplip.conf file. The proper ~/.hplip/hplip.conf file
is there with correct data. I delete it with a rm command in my boot
script (/etc/profile.d/bash.sh). How can this be fixed? (A minor
display annoyance otherwise.)

Please note also that the latest version now needs libtiff to build.
That is not in your system requirements section.

And, finally, it's great that you got rid of the hp daemons. But, why
not stop python as well? Python remains resident after the first
invocation of any hplip use.

Thanks.

Richard David Sherman
2007 June 30

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
HPLIP-Help mailing list
HPLIP-Help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hplip-help

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
HPLIP-Help mailing list
HPLIP-Help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hplip-help

Reply via email to