Page 3 of 3

Re: Script to make Slackware Compliant package of xz, deb

Posted: 08 Oct 2016, 21:19
by Bogomips
@FURRY_NOVA Thanks for clarification. There's more than one way to skin a cat! :)
FURRY_NOVA wrote:In the File System, that contains bin, dev, etc and home and stuff. It has a node-v4.6.0-linux-x86 folder. The contents of that folder should be outside in the File System.

Current:

Code: Select all

/node-v4.6.0-linux-x86/include/
/node-v4.6.0-linux-x86/bin/
/node-v4.6.0-linux-x86/share/
/node-v4.6.0-linux-x86/README.md
/node-v4.6.0-linux-x86/lib/
/node-v4.6.0-linux-x86/CHANGELOG.md
/node-v4.6.0-linux-x86/LICENSE
Should be:

Code: Select all

/include/
/bin/
/share/
/README.md
/lib/
/CHANGELOG.md
/LICENSE
Starting back at the tar.xz. I made the file structure look like the last code area above this paragraph with Xarchiver application. I deleted README.md, CHANGELOG.md and LICENSE since those aren't created in File System when activating other modules. I don't know if they supposed to be places somewhere else though.
The story so far (Have to do better job of renaming. So far sorted the debs.):
  • Code: Select all

    guest@porteus:~$ sh xz2txz.sh -nv node-v4.6.0-linux-x86.tar.xz
    ->  node-v4.6.0-linux-x86.x-z-z-.txz
    <slack-desc>
    node-v4.6.0-linux-x86.tar.x: (node-v4.6.0-linux-x86.tar.xz)
    
    Slackware package maker, version 3.141593.
    
    Searching for symbolic links:
    node-v4.6.0-linux-x86/bin/npm	../lib/node_modules/npm/bin/npm-cli.js
    
    Making symbolic link creation script:
    ( cd node-v4.6.0-linux-x86/bin ; rm -rf npm )
    ( cd node-v4.6.0-linux-x86/bin ; ln -sf ../lib/node_modules/npm/bin/npm-cli.js npm )
    ...
    Removing symbolic links:
    removed './node-v4.6.0-linux-x86/bin/npm'
    ...
    Slackware package /home/guest/node-v4.6.0-linux-x86.x-z-z-.txz created.
    
    Installation Files List: /tmp/Sat_21:50/xz_5845.lst
    ______________________________________________________________________________
    root@porteus:/home/guest# txz2xzm node-v4.6.0-linux-x86.x-z-z-.txz
    Verifying package node-v4.6.0-linux-x86.x-z-z-.txz.
    Installing package node-v4.6.0-linux-x86.x-z-z-.txz:
    PACKAGE DESCRIPTION:
    Executing install script for node-v4.6.0-linux-x86.x-z-z-.txz.
    Package node-v4.6.0-linux-x86.x-z-z-.txz installed.
    
    Creating /home/guest/node-v4.6.0-linux-x86.x-z-z-.xzm
    
    root@porteus:/home/guest# activate node-v4.6.0-linux-x86.x-z-z-.xzm
    Quiet mode: off
    Adding 10 new loop devices
    Updating shared library links:  /sbin/ldconfig
    
  • Code: Select all

    guest@porteus:~$ which node
    which: no node in (/usr/local/bin:/usr/bin:/bin:/usr/games:/opt/porteus-scripts:/usr/lib/qt/bin:/usr/lib/qt/bin:/usr/lib/qt/bin)
    
    guest@porteus:~$ ls /
    M/    etc/   media/                  opt/   run/   sys/  var/
    bin/  home/  mnt/                    proc/  sbin/  tmp/
    dev/  lib/   node-v4.6.0-linux-x86/  root/  srv/   usr/
    
    guest@porteus:~$ PATH+=:/node-v4.6.0-linux-x86/bin/
    guest@porteus:~$ which node
    /node-v4.6.0-linux-x86/bin/node
    
    guest@porteus:~$ node
    > console.log("hi");
    hi
    undefined
    > guest@porteus:~$
    
    or

    Code: Select all

    guest@porteus:~$ which node
    which: no node in (/usr/local/bin:/usr/bin:/bin:/usr/games:/opt/porteus-scripts:/usr/lib/qt/bin:/usr/lib/qt/bin:/usr/lib/qt/bin)
    
    guest@porteus:~$ /node-v4.6.0-linux-x86/bin/node 
    > console.log("hi");
    hi
    undefined
    > guest@porteus:~$ 
    
    :wink:
FURRY_NOVA wrote:Then used your script to convert to txz where it shows:

Code: Select all

/install/
/include/
/bin/
/share/
/lib/
/./
Then I txz2xzm it, activated xzm and tried it again:

Code: Select all

guest@porteus:~$ node
> console.log("hi");
hi
undefined
>  

Re: Script to make Slackware Compliant package of xz, deb

Posted: 08 Oct 2016, 21:26
by brokenman
I read no malice in Bogomips post at all. Just neutral facts. In fact, if EVERYBODY followed his advice development would come much easier and faster.

It is one thing to just report a bug. (Hey man, XYZ don't work. I tried to start it and it gave an error.)
It is quite another thing to dig deeper, find the error and give advice about fixing it. This is what helps the community more. It is the way Bogomips reports bugs and, for the most part, FURRY_NOVA usually does too. Thanks guys!

PS: I usually don't like to make noise in threads, however, I felt the need here to reinforce correct bug reporting procedure.

Re: Script to make Slackware Compliant package of xz, deb

Posted: 11 Oct 2016, 10:18
by francois
@brokenman and bogomips:
Agreed upon that topic of being more constructive. This saves work to the developper and help forum members to get a bigger IT IQ. :twisted:

Re: Script to make Slackware Compliant package of xz, deb

Posted: 07 Jan 2019, 16:23
by Rava
Bogomips wrote:
28 Apr 2015, 18:06
Paste above script into text editor. Save once as xz2txz.sh. Save again as deb2txz.sh. Save once more as rpm2txz.sh.
I presume having one version of the script (the newest one of course) in $PATH and the others just softlinks to that one copy will work as well?

Re: Script to make Slackware Compliant package of xz, deb

Posted: 07 Jan 2019, 22:28
by Ed_P
So, how did your testing turn out?