LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-02-2016, 04:20 AM   #121
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921

joenew --

I like bassmadrigal's idea of placing the printer install script 'out of tree', like Alien Bob's mkinitrd_command_generator.sh script.

For example in say, /usr/share/

You would want a new directory rather than simply placing in the 'root' of /usr/share/ ...

Maybe add a new directory to the Package like /usr/share/Brother/ ?

And place your script in ( ?? something like ?? ) /usr/share/Brother/install-hl2030.sh ??

Then, add a BLURB in the README like say, 'turn on the printer ; log in as root ; type: /usr/share/Brother/install-hl2030.sh

Or something

OTOH, your Package ( brother-hl2030-2.0.1-i386-1hb.txz ) already includes the /usr/doc/brother-hl2030-2.0.1/ directory.

Maybe place the installer script in there with the README and the SlackBuild and write a corresponding note in the README ?

Either way, it's your SlackBuild so ultimately it's your call

Finally, I understand now what you mean that there is no need to override the $port or the $PRINTERNAME.

Thanks !

-- kjh
 
Old 11-02-2016, 06:37 AM   #122
joenew
Member
 
Registered: Mar 2010
Distribution: slackware 14.2 64bit
Posts: 149

Rep: Reputation: 21
I find /usr/share/Brother/ fitting better than /usr/doc/brother-hl2030-2.0.1/ for the setup script. I would name it setup-hl2030.sh.
Ok, I'll upload the updated version as soon.
Thanks a lot again!
 
Old 11-03-2016, 06:49 AM   #123
joenew
Member
 
Registered: Mar 2010
Distribution: slackware 14.2 64bit
Posts: 149

Rep: Reputation: 21
Ok, I made some changes based on our previous messages:
1- README-build is now more verbose, with "download notes", "arch dependent build notes", "requirements", "post install printer setup".
2- doinst.sh has been removed. The operations of printer setup are now extracted from cupswrapper script and placed in the script /usr/share/Brother/setup-hl2030.sh (for this script I set owner root and permissions 744: only root, the owner, can execute it... Hope this is a good choice, what do you think?).

If you are "english spoken" let me know if you find language related mistakes in README, slack-desc or in comments of the SlackBuild.

You can download the build tarball at:
https://www.dropbox.com/s/1eyj9o1q6s...03.tar.gz?dl=0


PS.
1.
These drivers are working on 32bit systems, 64bit system with multilibs installed... but what about ARM architecture? Is there a way to install 32bit binaries on ARM, for instance with some "arm multilib", as we do for 64bit systems?

2.
If we want to add a "brother-hl2030.info" file, what packages would we have to put in "REQUIRES=" line?
 
Old 11-03-2016, 01:00 PM   #124
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
joenew --

Built x86_64 and i386 Packages.

Very Nice !

Very Clean !

As for the SBo.info file ... boy howdy ... I am not sure what's REQUIRED.

The 32-bit binary on 64-bit Systems is covered in the README so maybe nothing is really REQUIRED ?

One thing I missed before is the 777 Permissions on usr/local/Brother/inf/

Probably came that way but ...

Code:
drwxrwxrwx root/root         0 2016-11-03 12:51 usr/local/Brother/inf/
There is a standard SlackBuild 'fixpermissions' snippet floating around that would clean that up nicely.

Thanks again !

-- kjh

Code:
# tar -tvf brother-hl2030-2.0.1-i386-1hb.txz

drwxr-xr-x root/root         0 2016-11-03 12:51 ./
drwxr-xr-x root/root         0 2016-11-03 12:51 var/
drwxr-xr-x root/root         0 2016-11-03 12:51 var/spool/
drwxr-xr-x lp/lp             0 2016-11-03 12:51 var/spool/lpd/
drwx------ lp/lp             0 2007-04-05 18:31 var/spool/lpd/HL2030/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/bin/
-rwxr-xr-x root/root     20872 2007-04-05 18:31 usr/bin/brprintconflsr2
-rwxr-xr-x root/root       191 2007-04-05 18:31 usr/bin/brprintconfiglpr2
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/local/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/local/Brother/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/local/Brother/cupswrapper/
-rwxr-xr-x root/root     17812 2007-04-10 00:32 usr/local/Brother/cupswrapper/cupswrapperHL2030-2.0.1
-rwxr-xr-x root/root     14212 2007-04-10 00:32 usr/local/Brother/cupswrapper/brcupsconfig3
drwxrwxrwx root/root         0 2016-11-03 12:51 usr/local/Brother/inf/
-rw-r--r-- root/root       651 2007-04-05 18:31 usr/local/Brother/inf/brHL2030func
-rw-r--r-- root/root       215 2007-04-05 18:31 usr/local/Brother/inf/paperinf
-rw-rw-rw- root/root       165 2007-04-05 18:31 usr/local/Brother/inf/brHL2030rc
-rwxr-xr-x root/root      1623 2007-04-05 18:31 usr/local/Brother/inf/setupPrintcap
-rwxr-xr-x root/root      5604 2007-04-05 18:31 usr/local/Brother/inf/braddprinter
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/local/Brother/lpd/
-rwxr-xr-x root/root      3150 2007-04-05 18:31 usr/local/Brother/lpd/psconvert2
-rwxr-xr-x root/root     15328 2007-04-05 18:31 usr/local/Brother/lpd/rawtobr2
-rwxr-xr-x root/root      7908 2007-04-05 18:31 usr/local/Brother/lpd/filterHL2030
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/local/Brother/filter/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/share/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/share/Brother/
-rwxr--r-- root/root       328 2016-11-03 12:51 usr/share/Brother/setup-hl2030.sh
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/share/cups/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/share/cups/model/
-rw-r--r-- root/root     10258 2016-11-03 12:51 usr/share/cups/model/HL2030.ppd
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/doc/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/doc/brother-hl2030-2.0.1/
-rw-r--r-- root/root      3230 2016-11-03 12:51 usr/doc/brother-hl2030-2.0.1/brother-hl2030.SlackBuild
-rw-r--r-- root/root      2748 2016-11-03 12:51 usr/doc/brother-hl2030-2.0.1/README-build
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/lib/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/lib/cups/
drwxr-xr-x root/root         0 2016-11-03 12:51 usr/lib/cups/filter/
-rwxr-xr-x root/root      4598 2016-11-03 12:51 usr/lib/cups/filter/brlpdwrapperHL2030
-rwxr-xr-x root/root     45104 2007-04-05 18:31 usr/lib/libbrcomplpr2.so
drwxr-xr-x root/root         0 2016-11-03 12:51 install/
-rw-r--r-- root/root       635 2016-11-03 12:51 install/slack-desc
 
Old 11-03-2016, 03:03 PM   #125
joenew
Member
 
Registered: Mar 2010
Distribution: slackware 14.2 64bit
Posts: 149

Rep: Reputation: 21
Those permissions are copied from Brother cupswrapper script:
Code:
chmod a+w /usr/local/Brother/inf/brHL2030rc
chmod a+w /usr/local/Brother/inf
I'm not sure, but probably that directory and that contained files have to be writable by anyone.
In my slackbuild I first set the slackware default permissions to all the package tree. Then I change owner and perms for each dir and file that requires a different setting.

I was reading something more about SBo gudelines:
https://www.slackbuilds.org/guidelines/
Quote:
REQUIRES contains a space-separated list of all required build-time and run-time dependencies, each named exactly as listed on the SlackBuilds.org site. It should not contain anything that is part of Slackware itself. The content of REQUIRES should only be first level dependencies (i.e. no deps of deps).
In this case we would have the three multilib packages, but they are required only for 64bit systems.
Obviously cups would be required, but it is included as part of slackware official packages repo.
So, in this case I think the REQUIRES string could be left empty... Isn't it?
 
1 members found this post helpful.
Old 11-04-2016, 02:43 AM   #126
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
joenew --

I've gone thru my local SBo 14.2 git repo and the only x86_64 Tagged Variables in any of the .info files are DOWNLOAD_x86_64 and MD5SUM_x86_64

I think you're good now.

You've got a keeper there !

Thank you

-- kjh

Code:
#
# look for variables in the SBo.info files with x86_64 tags and print the unique list 
#
# cd /home/dld/slackbuilds/14.2
# find . -type f -iname "*.info" -exec grep -H x86_64 {} \; |gawk -F ':' '{ print $2 }' |gawk -F '=' '{ print $1 }' |sort -u
                 http
                 http
DOWNLOAD_x86_64
MD5SUM_x86_64
 
Old 11-04-2016, 05:50 AM   #127
joenew
Member
 
Registered: Mar 2010
Distribution: slackware 14.2 64bit
Posts: 149

Rep: Reputation: 21
Thank you for your reply!

PS.
Just out of interest...
Quote:
you've got a keeper there!
What does it mean?
 
Old 11-04-2016, 06:20 AM   #128
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
Sorry joenew ...

A 'keeper' is 'a good one' ( as in fishing: keep the fish, do not throw it back )

-- kjh
 
Old 11-04-2016, 06:28 AM   #129
joenew
Member
 
Registered: Mar 2010
Distribution: slackware 14.2 64bit
Posts: 149

Rep: Reputation: 21
I understand!

Ok, so:
I'll modify my Slackbuild again, to be closer to SBo guidelines.
I'll add the ".info" file and rename README-build to README.
When I'll have done I'll post there a link to the new tarball for a final check.
And finally I'll try to upload to SBo, so that it will be provided to all other slackers. I think it's the best choice cause that is a popular repository for slackware users.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] brother printer drivers randyvh Linux - Newbie 5 10-09-2015 06:01 PM
Brother DCP-J4110DW printer-Drivers Nuffield Linux - Newbie 2 02-06-2015 06:59 PM
Drivers for Brother MFC J430 w printer jbander Linux - Hardware 1 07-26-2013 07:44 PM
Unable to install Brother printer drivers siouxzieq Linux - Hardware 8 01-04-2012 04:35 PM
Brother Printer Drivers Site Down Michael Johnson Linux - General 1 07-21-2005 01:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:32 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration