HOWTO: Printing under porteus 3.2 (proposal)

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
francois
Contributor
Contributor
Posts: 5291
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Y fait frette et on gèle

Re: HOWTO: Printing under porteus 3.2 (proposal)

Post#16 by francois » 11 Oct 2016, 11:04

Thanks. I will do that.

1.0 In addition, in my working folder as I want to use only txz to finally produce the ending printing module with command, I have been able to use rpm2txz. There is an error message. Is it important (rpm2cpio failed) as the .txz (slackware) package was built anyway?

Code: Select all

root@porteus:/home/guest/Downloads# rpm2txz bjfilter-common-2.50-3.i386.rpm bjfilter-common-2.50-3.i386.rpm.txz

Slackware package maker, version 3.141593.

Searching for symbolic links:

No symbolic links were found, so we won't make an installation script.
You can make your own later in ./install/doinst.sh and rebuild the
package if you like.

This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!

Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n

Creating Slackware package:  /home/guest/Downloads/bjfilter-common-2.50-3.i386.txz

./
usr/
usr/local/
usr/local/bin/
usr/local/bin/bjcups
usr/lib/
usr/lib/cups/
usr/lib/cups/backend/
usr/lib/cups/backend/canon_usb
usr/lib/cups/backend/canon_parallel
usr/lib/cups/filter/
usr/lib/cups/filter/pstocanonbj

Slackware package /home/guest/Downloads/bjfilter-common-2.50-3.i386.txz created.

ERROR:  rpm2cpio failed.  (maybe bjfilter-common-2.50-3.i386.rpm.txz is not an RPM?)
root@porteus:/home/guest/Downloads#
2.0 Is there away to use deb2txz under porteusor shall I simply merge modules way:
OK found it deb2targz:
https://github.com/jbarrett/deb2tgz
Carpe diem.




User avatar
Blaze
DEV Team
DEV Team
Posts: 1647
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: HOWTO: Printing under porteus 3.2 (proposal)

Post#17 by Blaze » 11 Oct 2016, 16:18

francois, what about

Code: Select all

rpm2xzm
deb2xzm
?
Linux porteus 4.13.3-porteus #1 SMP PREEMPT Sat Sep 23 18:22:13 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
francois
Contributor
Contributor
Posts: 5291
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Y fait frette et on gèle

Re: HOWTO: Printing under porteus 3.2 (proposal)

Post#18 by francois » 11 Oct 2016, 20:34

@brokenman:
gimp-solibs was not into gimp
Maybe there is a way to build gimp to get solibs applied, and that was handy for ahau to use it. I think you might do that with linux from scratch.

There is glc-solibs as a slackware package:
http://www.slackware.com/~alien/multilib/?C=S;O=A

openssl-solibs as slax module:
http://www.slax.org/modules.php?q=opens ... ory=search

and others unde pkgs.org all in slackware 13.2:
https://pkgs.org/search/solibs

@blaze:
Hello blaze. You are right these are good. Then I could use freestyler mergemodules script. :)

But I wanted to work with txz only this time to be able to use the faq strategy (ahau, brokenman or fanthom`s):
http://www.porteus.org/component/conten ... udies.html

Code: Select all

installpkg -root ~/temp/modwork/printing *.txz


It is under control now 8)
Carpe diem.

User avatar
francois
Contributor
Contributor
Posts: 5291
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Y fait frette et on gèle

Re: HOWTO: Printing under porteus 3.2 (proposal)

Post#19 by francois » 11 Oct 2016, 20:53

solibs seems to stand for so libraries, the enigma if it solved means that ahau used the so libraries of gimp. I will try that.
Carpe diem.

Post Reply