gslapt GUI

[bigbass]

I have this installed in Porteus 1.2

Glsapt is used by many slackware based distros
http://en.wikipedia.org/wiki/Slapt-get


DISCLAIMER
It is a tool to install packages plus many more built in advanced features
just like any power tool care must be used not to cause damage to the user
so I present this as an option not a solution
it can be installed and used but a lot of fine tuning would be needed to make it work "perfectly"
with Porteus (I don't claim that the word perfectly does exist or it is implied here since package management still requires system administration and proper set up and careful use )

but all that aside I am happy to say this works

Why ?
I would like to try some of the other options that have become popularized
and used by a few slackware based distros
this doesn't imply dissatisfaction to the way slackware installs packages or the way Porteus installs
modules

it is just a tool that could be used to compliment things
on a personal level for me as a development tool for when we switch over to slackware 14

there are just a few dependencies to get this to run
after some more testing I will list what is needed and a mini how to get started
I already have a script to add Porteus packages to the PACKAGES.TXT
but I am currently only using the official default setup for now
so I can see if anything is still missing or not



This gets you a vanilla install no modified files 32bit
http://bigbass-porteus.googlecode.com/f ... i386-1.tgz
http://bigbass-porteus.googlecode.com/f ... i386-1.tgz
http://bigbass-porteus.googlecode.com/f ... i486-1.txz
http://bigbass-porteus.googlecode.com/f ... i486-1.txz
http://bigbass-porteus.googlecode.com/f ... i486-1.txz
http://bigbass-porteus.googlecode.com/f ... h-1stb.tgz


For a basic setup with dependency resolving point to slacky with this in /etc/slapt-get/slapt-getrc
32bit I blocked KDE since TDE is installed you will see where

Code: Select all

WORKINGDIR=/var/slapt-get
EXCLUDE=^aaa_elflibs,^devs,^glibc-.*,^kernel-.*,^udev,.*-[0-9]+dl$,x86_64,^kde,^koffice*
SOURCE=ftp://ftp.slackware.com/pub/slackware/slackware-13.37/:OFFICIAL
SOURCE=http://software.jaos.org/slackpacks/13.37/:CUSTOM
SOURCE=http://repository.slacky.eu/slackware-13.37/:PREFERRED

This is just to get started

Joe

[Hamza]

Wonderful !

[brokenman]

Awesome! I will also add that bigbass also went the extra yards and presented me with the code to integrate this with the current porteus package management system. At first glance it looks viable as an alternative to our current package management system. Thanks bigbass!

[francois]

Nice post.

Last year while we were talking about adopting or developing a package manager I made a thread called : Using gslapt as a package manager:
http://porteus.org/forum/viewtopic.php? ... lapt#p9217

It might present some complementary information.

PPM has really some interesting and unique features. Please do not let it down brokenman.

Maybe the best thing that could be done for gslapt would be to come out with a list of the fastest and most diversified package repositories.

Gslapt is the package mnager for salix but also for zenlive if I am not wrong. Salix proposes the use of sourcery to build packages from source. This might be an interesting package builder for our users:

[bigbass]

Maybe the best thing that could be done for gslapt would be to come out with a list of the fastest and most diversified package repositories.

Ok we have that ,and making a list of all packages that work correctly with the Porteus base
this will take some time

The best part will be making our own in house repo to add to gslapt

Everything takes time but this is moving quickly much faster than I expected
maybe because I resisted change for too many years I am an old world
compile and install guy but there is a lot of advancements we can unite together
this is more than just doable the question now is just doing things right
so we can remain compatible this is why I will adjust anything to maintain
compatibility to Porteus

I forgot to say I updated the first post with packages to get a quick set up

For anything to work requires people we have a large slackware community
including its derivatives those that make packages that are compatible across many versions
advance the community ( I personally still dislike python and large QT apps but if they work well they could be an option for someone else I won't filter them out they will be lower on my need to test list ) some I may need to use also The idea is just find packages that work and let the people decide what they want to install

Joe

[francois]

I completely agree with you.

Posted after 1 day 5 hours 48 minutes 58 seconds:
You give me the motivation to get back on gslapt. Thats very good.

[bigbass]

I figured out how to add a repo of official slackware with changes and patches and add dependencies to it
this is more than a link it sets up the fake repo that links to a real repo that doesnt have dependencies
but the files that are installed convert the repo as though it was built with dependency info
this could be done also for slackware 14



http://bigbass-porteus.googlecode.com/f ... 6_PORT.tgz

you install this like a package and you need to manually
add this to /etc/slapt-get/slapt-getrc
SOURCE=file:///usr/src/slackware-13.37-with-deps/:CUSTOM


Joe

[bigbass]

Well I am surprised that there weren't many posts or reports from testers
so I decided to make it even easier to test out

auto download install and set up gslapt script



boot always fresh just to see that nothing will hurt your system

then paste this code into a text editor that fixes the formatting then run this script in a terminal it will do everything for you
you just need to find gslapt in the menu and run it thats it
gslapt is in system if you use XFCE and TDE

I am on a live XFCE for testing tested TDE also

look for realplayer and install it if you want to test a package just check the little box install and execute
then look in the menu and there it is easy

I even threw in an official slackware site I generated with dependencies
I made a fake repo in /usr/src that does all the hard work without having to
upload any packages to a website

Joe
===============================================

Code: Select all

#!/bin/bash


# auto download install and set up gslapt 
# Joe Arose ... bigbass   


mkdir -p /tmp/gslapt-auto-setup
cd /tmp/gslapt-auto-setup
wget -N http://bigbass-porteus.googlecode.com/files/gslapt-0.5.3f-i386-1.tgz
wget -N http://bigbass-porteus.googlecode.com/files/slapt-get-0.10.2m-i386-1.tgz
wget -N http://bigbass-porteus.googlecode.com/files/curl-7.21.4-i486-1.txz
wget -N http://bigbass-porteus.googlecode.com/files/gpgme-1.3.0-i486-1.txz
wget -N http://bigbass-porteus.googlecode.com/files/libassuan-2.0.1-i486-1.txz
wget -N http://bigbass-porteus.googlecode.com/files/requiredbuilder-0.16.5-noarch-1stb.tgz
wget -N http://bigbass-porteus.googlecode.com/files/slack_repo_with_deps-13.37-i486-6_PORT.tgz

installpkg *.t?z

cat << 'EOF' >/etc/slapt-get/slapt-getrc

WORKINGDIR=/var/slapt-get
    EXCLUDE=^aaa_elflibs,^devs,^glibc-.*,^kernel-.*,^udev,.*-[0-9]+dl$,x86_64,^kde,^koffice*
    #SOURCE=ftp://ftp.slackware.com/pub/slackware/slackware-13.37/:OFFICIAL
    SOURCE=http://software.jaos.org/slackpacks/13.37/:CUSTOM
    SOURCE=http://repository.slacky.eu/slackware-13.37/:PREFERRED
    SOURCE=file:///usr/src/slackware-13.37-with-deps/:CUSTOM

EOF



# update your local package cache to help you get started correctly 
slapt-get --update


# 
# launch slaptget GUI from the menu system in XFCE and in TDE 
# or from the command line with gslapt

[brokenman]

Works just like he says it does. A pleasure to use. Be sure to fix the formatting when pasting this into a text editor as the cat > file << EOF command MUST reside at the start of the line. The codebox here screws that up. Also remember to run script as root or installpkg won't run.

Thanks for the lazy way bigbass.

[fanthom]

@bigbass

tried and liked.
any chance to tweak gslap to work with .xzm modues instead of .txz packages?
and use 'activate' instead of 'installpkg'?

[francois]

Humm! The suggestion of fanthom would make gslapt as a very strong package manager candidate. What do you think bigbass?

[brokenman]

gslapt works from the standard slackware repository structure which means the best we can hope for is to append the script to convert packages after download.

[bigbass]

Hey guys



While hacking the sources is possible . I wouldn't want to maintain a fork of gslapt it is a mature app .The better way is to write a wrapper that looks at what you installed using gslapt (this is what brokenman suggested above) and roll it into a compatible xzm module following all the rules that were established for modules and in this way it is just a development tool to help test packages that may end up included in the porteus repo

but a wrapper to convert to modules is still something I would "help" develop
it is already done using txz2xzm I just mean the part of logging what gets installed with gslapt and offering a 2module option so the live testing could be easily saved

Joe

[fanthom]

The better way is to write a wrapper that looks at what you installed using gslapt (this is what brokenman suggested above) and roll it into a compatible xzm module following all the rules that were established for modules

this is actually a showstopper for me.
please convert libreoffice to xzm and tell me how long did it take. now please imagine an user with Atom CPU.
i prefer to do it once on my PC and push 'ready-to-go' module to porteus repo which can be activated within a second.

i would stick to PPM as default package manager for porteus.

[bigbass]

"it is just a development tool to help test packages that may end up included in the porteus repo"



These are the goals
1.) "Help" the developers get modules in the repo
2. )Lighten the work load so if you or one of the other developers want to go see a show with your family
and someone wants a new app...

3.)Help the advanced end users get in the game and help test some things that could get included as modules

it would take the end user with no help after the initial download (depending on there connection speed)
about 3minutes and thirty second to fully install libreoffice compared to

lets use one worst case scenario libreoffice
one of the members of porteus seeing a requested app then making the module and uploading it to the server
now if we multiply this by every module in the repo for porteus 1.2 to rebuild the whole repo I dont know how much personal time that takes and bandwidth needed
so the end user in a worst case scenario would have to wait after download 3 minutes and thirty seconds
to use a new version of libreoffice

until an official module was made and tested
I think this tool will only "help" meet some of those goals

a bonus link talking about libreoffice-3-6-2
http://alien.slackbook.org/blog/libreof ... -released/

Joe