vonbiber --
Just now downloaded your latest brotherdcp7030.SlackBuild and rebuilt brotherdcp7030-2.0.2_1-i386-1_vbi.txz
I checked the content of the Package.tgz file and the doinst.sh script.
It looks great !
The x86_64readme.txt file is very clear -- this package is 32-bit-only and x86_64readme.txt tells me exactly what I would need to do to be able to run on a pure-64-bit Slackware Machine.
Everything in the package seems to be in the correct directory and the install/doinst.sh script oughta work as expected.
Thanks for the new SlackBuild. It's a keeper !
offgridguy --
In addition to vonbiber's recommendations, this is how I approach new SlackBuilds ...
I think you've mentioned all the off-site info I know about.
One more thing you might want to look at on your Slackware Machine is: man makepkg
Lot's of tasty tidbits in there straight from the horse's mouth (
volkerdi
).
Another thing I LOVE about Slackware is that volkerdi's Package Management tools are Shell Scripts !
One can browse his *pkg scripts to see how they work ( and learn some handy scripting tricks too
)
Moreover, the Package DataBase on Slackware is a set of text files in /var/log/packages/
If you've ever hosed your YUM DataBase on a RHEL, CentOS, or Fedora Box, you'll REALLY appreciate the text file DataBase on Slackware !!!
Another nice thing about SlackBuilds is that ALMOST ALL of them are non-destructive ( vonbiber's SlackBuild is non-destructive ).
IOW, you won't affect your machine by simply running vonbiber's brotherdcp7030.SlackBuild Script as long as you've got enough disk space.
There are exceptions to the ALMOST ALL rule.
Be careful with taking SlackBuilds from unknown sources.
Look at the SlackBuild Script before you run it !
If you can't inspect the SlackBuild Script ( say it is compiled or otherwise obfusticated ), then don't run it on your System unless you KNOW for sure what it does !
As a rule, if you stick to official Slackware SlackBuilds and SlackBuilds from SlackBuilds.org, you'll be OK.
Once you've got a Package, you can look inside the .t?z file with a simple tar -tvf command ( see below[1] ).
Many, if not most Packages will include an install/doinst.sh script which I often check before I run installpkg on the new Package ( see below[2] )
Once you've verified the contents of the Package and maybe looked at the doinst.sh script, installation can be as simple as installpkg <<PkgName>> or upgradepkg --install-new <<PkgName>>
If you use one of the advanced Package Managers like slackpkg I am not sure how to proceed ...
I am a luddite when it comes to my Package Management ( I only use volkerdi's tools ) so I don't know how the advanced systems work with non-standard Packages.
Maybe others can help with that ...
HTH.
-- kjh
#
# below[1] - these are the contents of vonbiber's brotherdcp7030-2.0.2_1-i386-1_vbi.txz Package
#
# note that `tar -tvf` simply lists the contents of a tar file
#
Code:
tar -tvf brotherdcp7030-2.0.2_1-i386-1_vbi.txz
Code:
drwxr-xr-x root/root 0 2016-09-10 03:29 ./
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/bin/
-rwxr-xr-x root/root 26313 2016-09-10 03:29 usr/bin/brprintconflsr2
-rwxr-xr-x root/root 191 2016-09-10 03:29 usr/bin/brprintconfiglpr2
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/share/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/share/Brother/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/share/Brother/cupswrapper/
-rwxr-xr-x root/root 17552 2016-09-10 03:29 usr/share/Brother/cupswrapper/brcupsconfig3
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/share/Brother/inf/
-rw-r--r-- root/root 166 2016-09-10 03:29 usr/share/Brother/inf/brDCP7030rc
-rw-r--r-- root/root 215 2016-09-10 03:29 usr/share/Brother/inf/paperinf
-rwxr-xr-x root/root 1623 2016-09-10 03:29 usr/share/Brother/inf/setupPrintcap
-rw-r--r-- root/root 652 2016-09-10 03:29 usr/share/Brother/inf/brDCP7030func
-rwxr-xr-x root/root 7976 2016-09-10 03:29 usr/share/Brother/inf/braddprinter
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/share/Brother/lpd/
-rwxr-xr-x root/root 3150 2016-09-10 03:29 usr/share/Brother/lpd/psconvert2
-rwxr-xr-x root/root 7909 2016-09-10 03:29 usr/share/Brother/lpd/filterDCP7030
-rwxr-xr-x root/root 20186 2016-09-10 03:29 usr/share/Brother/lpd/rawtobr2
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/share/cups/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/share/cups/model/
-rwxr-xr-x root/root 10265 2016-09-10 03:29 usr/share/cups/model/DCP7030.ppd
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/doc/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/doc/brotherdcp7030/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/doc/brotherdcp7030/SlackBuild/
-rw-r--r-- root/root 5101 2016-09-10 03:29 usr/doc/brotherdcp7030/SlackBuild/brotherdcp7030.SlackBuild
-rw-r--r-- root/root 424 2016-09-10 03:29 usr/doc/brotherdcp7030/SlackBuild/readme.txt
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/lib/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/lib/cups/
drwxr-xr-x root/root 0 2016-09-10 03:29 usr/lib/cups/filter/
-rwxr-xr-x root/root 4579 2016-09-10 03:29 usr/lib/cups/filter/brlpdwrapperDCP7030
-rwxr-xr-x root/root 53606 2016-09-10 03:29 usr/lib/libbrcomplpr2.so
drwxr-xr-x root/root 0 2016-09-10 03:29 install/
-rw-r--r-- root/root 1076 2016-09-10 03:29 install/slack-desc
-rw-r--r-- root/root 322 2016-09-10 03:29 install/doinst.sh
#
# below[2] -- note that vonbiber's Package includes an install/doinst.sh file in the listing above. What does it do ?
#
# extract the contents of the install/ directory from the Package into some tmp/ directory
#
Code:
/home/dld/Brother/vonbiber-Brother-7030-SlackBuild # note THIS
Code:
mkdir tmp
cd tmp
tar -xvf ../brotherdcp7030-2.0.2_1-i386-1_vbi.txz install
#
# what is in install/doinst.sh ?
#
Code:
cat install/doinst.sh
Code:
if [ ! -e /var/spool/lpd ]
mkdir /var/spool/lpd
chgrp --reference=/var/spool/cups -R /var/spool/lpd
chmod --reference=/var/spool/cups -R /var/spool/lpd
fi
mkdir -p /var/spool/lpd/DCP7030
chgrp --reference=/var/spool/cups/tmp -R /var/spool/lpd/DCP7030
chmod --reference=/var/spool/cups/tmp -R /var/spool/lpd/DCP7030
#
# looks safe enough ... nothing like rm -rf / is in there
#
# optional -- clean up the mess I made ...
#
Code:
pwd # make SURE I am where I think I am
Code:
/home/dld/Brother/vonbiber-Brother-7030-SlackBuild/tmp
Code:
cd ..
pwd # where am I NOW ?
Code:
/home/dld/Brother/vonbiber-Brother-7030-SlackBuild
#
# looks ok ... clean up ...
#
Code:
rm -rf tmp # NOTE THE RELATIVE PATH ! ( no leading slashes here )