cruxports4slack

[uelsk8s]

cruxports4slack: cruxports4slack-20061113 Crux ports system for Slackware
cruxports4slack:
cruxports4slack: With cruxports4slack you can use the crux ports system
cruxports4slack: with Slackware.
cruxports4slack:

Vec found this and I modified it to use makeslapt and our default CFLAGS
you can get the VL modified version here: http://vectorlinux.osuosl.org/Uelsk8s/cruxports4slack-20061113-i586-3vl59.tlz
It should build good VL packages. Some of the build scripts need work, and all can be modified pretty easily
If you have any questions just post here
This should be a big help for our packagers

Uelsk8s

[exeterdad]

Oh Dear Lord!  I'm running ports -u right now and it's going, and going, and goooooooing!  I must admit I'm a bit scared of it.  How would a VL package be built.  And how would we submit the sources?

[uelsk8s]

ports -u, upgrades your ports tree
then you cd to /usr/ports/contrib/PackageYouwantToBuild
make any needed changes to the Pkgfile
and run pkgmk -d
when its done submit the whole dir

Running
=======

pkginfo
-------
usage: pkginfo [-i|-i package]
options:
    -i, --installed        list installed packages and their version.
    -l, --list package     list  files  owned  by  the  specified package
    -h                     print help and exit



ports
-----
usage: ports [options] [collection ...]
options:
    -u, --update    update ports
    -l, --list      list available ports
    -d, --diff      list differences between installed packages and availabe ports
    -v, --version   print version and exit
    -h, --help      print help and exit


pkgmk
-----
usage: pkgmk [options]
options:
    -i,   --install             build and install package
    -u,   --upgrade             build and install package (as upgrade)
    -r,   --recursive           search for and build packages recursively
    -d,   --download            download missing source file(s)
    -do,  --download-only       do not build, only download missing source file(s)
    -utd, --up-to-date          do not build, only check if package is up to date
    -um,  --update-md5sum       update md5sum
    -im,  --ignore-md5sum       build package without checking md5sum
    -cm,  --check-md5sum        do not build, only check md5sum
    -ns,  --no-strip            do not strip executable binaries or libraries
    -f,   --force               build package even if it appears to be up to date
    -c,   --clean               remove package and downloaded files
    -p,   --pkgfile       use alternative Pkgfile
    -kw,  --keep-work           keep temporary working directory
    -cf,  --config-file   use alternative configuration file
    -v,   --version             print version and exit
    -h,   --help                print help and exit
            

Example for building and installing a package
   
    cd /usr/ports/contrib/antiword
    pkgmk -i

Enjoy!

from http://delili.lens.hl-users.com/cruxports4slack.html

[exeterdad]

I have to say it is a pretty cool system.  Be careful, you might be building older version packages though as some of the Pkgfile's are pretty stale.

I've modded my pkgmk script even further:

1. It prompts you for your packager name, or uses VL_PACKAGER if its set in the enviorment. This is used in feature #2.
2. It appends our usual build info to the bottom of the slack-desc. (./config, packager, CFLAGS, etc.)
3. It will use a pre-made slack-desc if it finds it in the directory, if not, it will create the vague one as usual.
4. I swapped out makeslapt with requiredbuilder and makepkg so I can get a copy of the slack-desc and slack-depends. These are left in the working directory.

Does this interest anyone else?

[uelsk8s]

It interests me
Required builder is so slow. if the only reason you are using it is to get a copy of the slack-desc and slack-depends file I can think if an easier way.
I also changed the version from "ver=vl6"  to    "if [ -z "$vlver" ];then vlver="$release"vl59; fi"

can you send me your changes and ill merge them into a new build?

I also forgot to mention that there are lots more ports repo's that you can add the searchable list is here http://crux.nu/portdb/

[exeterdad]

can you send me your changes and ill merge them into a new build?

Sure! http://pastebin.com/m59080ae5

I also forgot to mention that there are lots more ports repo's that you can add the searchable list is here http://crux.nu/portdb/

Already discovered it  But Thanks!

[uelsk8s]

here is the updated package: http://vectorlinux.osuosl.org/Uelsk8s/cruxports4slack-20061113-i586-3vl59.tlz

I switched back to makeslapt as default, so if you want to use requiredbuilder and makepkg just set RB=yes before running pkgmk

[exeterdad]

I switched back to makeslapt as default, so if you want to use requiredbuilder and makepkg just set RB=yes before running pkgmk

Nice.  I like your added "RB=yes" switch so users can use what they like.

I took our little "project" a bit further.  Based off of your latest pkgmk I made these changes.

1) Prettied up the "Add your name" prompt.  Also relocated it so user won't have to enter their name to view --help. 
2) Requiredbuilder/makepkg can be invoked by using -rb or --requiredbuilder or "RB=yes"
3) User can make packages for 5.8, 5.9, or 6.0 by using -vl58, --vl58, -vl59, --vl59, -vl60, --vl60.  But vl59 is still the default if nothing is specified.
4) Updated --help So our new settings aren't hidden/secret.

also a lil bugfix in my earlier code.  I did modify your "vlver" switch.  I needed one as well and thought it better to modify yours rather then add one more.

Here's the complete (updated) pkgmk file:
http://pastebin.com/f336eebd4

[uelsk8s]

I added your pkgmk and updated the package to: http://vectorlinux.osuosl.org/Uelsk8s/cruxports4slack-20061113-i586-4vl59.tlz
I also updated the repo lists so make sure to use ports -u to get the latest

[exeterdad]

If we keep dinking with the thing it's going to become cruxports4vl 

[M0E-lnx]

Guys, as many of you have seen, I'm working on a GUI for cruxports4slack, but I'm having a little problem with this.

My problem is with this section of the script

Code:

ARCH=$(uname -m)
        case "$ARCH" in
          (i?86) ARCH=i586
            CPU=i586
            CONFIGURE_TRIPLET=i486-slackware-linux
            ;;

          (x86_64) CPU=$ARCH

            CONFIGURE_TRIPLET=x86_64-pc-linux

            ;;
     esac

On my laptop, uname -m returns 'i686'. But this script seems to force i586.
Has anyone tested this on an i486 machine and see what it does?
Has anyone thought of a better way to make this determine the architecture? or can I assume it will always force i586?

[saulgoode]

The $ARCH variable doesn't directly dictate the CPU optimization because the CFLAGS are set to "-march=i586 -mtune=i686" (which are the Vector required values according to this HOWTO).

@Uelsk8s, would it not be better to rename the package to 'cruxports4vec' (or somesuch). With the modifications, it no longer builds Slackware packages.

[stoichyu]

Guys, as many of you have seen, I'm working on a GUI for cruxports4slack, but I'm having a little problem with this.

My problem is with this section of the script

Code:

ARCH=$(uname -m)
        case "$ARCH" in
          (i?86) ARCH=i586
            CPU=i586
            CONFIGURE_TRIPLET=i486-slackware-linux
            ;;

          (x86_64) CPU=$ARCH

            CONFIGURE_TRIPLET=x86_64-pc-linux

            ;;
     esac

On my laptop, uname -m returns 'i686'. But this script seems to force i586.
Has anyone tested this on an i486 machine and see what it does?
Has anyone thought of a better way to make this determine the architecture? or can I assume it will always force i586?

You can assume it to force i586 for ix86 architectures since the case(switch) statement is (i?86). Also, I think build scripts overwrite the environment set CFLAGS.

[M0E-lnx]

ok thanks. I have adjusted my gambas code to do the same.

[blurymind]

this should be packaged together with vlpackager