[IMPORTANT] Package manager for next release
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: [IMPORTANT] Package manager for next release
Originally i just knocked up this script for my own use so we could start to get modules produced. It wasn't meant for official release but i guess it could be polished and included.
1) 'switch to root' function is missing so guest wont be able to use this tool properly. please add this to the begining of script:
# Switch to root
if [ `whoami` != "root" ]; then
xterm -e su - -c "/usr/bin/slackonverter.sh"
exit
fi
Thanks. I've been looking for a way to use this function with Xdialog.
3) deps are not resolved automatically. are you planing to implement this feature?
I could include dep resolution with this as it uses slacky repo which lists dependencies. As is said i wasn't planning it but could put some work in and produce it.
4) 'Search package by string' function requires to press 'OK' while 'enter' would be more functional (not sure if it's Xdialog limitation)
Appears to be Xdialog. Another annoying thing is you can't press a keyboard letter and jump to the letter in the list of packages.
5) at every package download you need to specify destination folder. i think it could be resolved like in 'modtools' with preferred destination.
Ok, this makes better sense. I was lazy because this was originally just for me.
6) after conversion user should get information about success/fail. some big packages like OpenOffice may fail while converted in aufs (not enough size).
OK.
7) after conversion unpacked dir and txz are not deleted (not sure if it was intended)
Will clean this up too. I generally leave the processed files there while testing script. Forgot to add cleanup function.
8 ) after conversion xzm module should have at least $arch variable in the name ($build probably makes not sense, or could be set to -1porteus) as it's easy to get confused with 'mplayer-1.0.0.xzm' while used in 32/64 bit editions.
Will add this.
9) 'Search package by category' window could be wider to be able to see all packages without scrolling.
1) 'switch to root' function is missing so guest wont be able to use this tool properly. please add this to the begining of script:
# Switch to root
if [ `whoami` != "root" ]; then
xterm -e su - -c "/usr/bin/slackonverter.sh"
exit
fi
Thanks. I've been looking for a way to use this function with Xdialog.
3) deps are not resolved automatically. are you planing to implement this feature?
I could include dep resolution with this as it uses slacky repo which lists dependencies. As is said i wasn't planning it but could put some work in and produce it.
4) 'Search package by string' function requires to press 'OK' while 'enter' would be more functional (not sure if it's Xdialog limitation)
Appears to be Xdialog. Another annoying thing is you can't press a keyboard letter and jump to the letter in the list of packages.
5) at every package download you need to specify destination folder. i think it could be resolved like in 'modtools' with preferred destination.
Ok, this makes better sense. I was lazy because this was originally just for me.
6) after conversion user should get information about success/fail. some big packages like OpenOffice may fail while converted in aufs (not enough size).
OK.
7) after conversion unpacked dir and txz are not deleted (not sure if it was intended)
Will clean this up too. I generally leave the processed files there while testing script. Forgot to add cleanup function.
8 ) after conversion xzm module should have at least $arch variable in the name ($build probably makes not sense, or could be set to -1porteus) as it's easy to get confused with 'mplayer-1.0.0.xzm' while used in 32/64 bit editions.
Will add this.
9) 'Search package by category' window could be wider to be able to see all packages without scrolling.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: [IMPORTANT] Package manager for next release
"I've been looking for a way to use this function with Xdialog."
i'm using "terminal" as Xdialog 'su' helper. every Xdialog app which needs 'switch to root' function need to be started from /usr/shared/applications/*.desktop
like that:
Exec=/tmp/.terminal -e xpns-tool.sh
i'm using "terminal" as Xdialog 'su' helper. every Xdialog app which needs 'switch to root' function need to be started from /usr/shared/applications/*.desktop
like that:
Exec=/tmp/.terminal -e xpns-tool.sh
Please add [Solved] to your thread title if the solution was found.
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: [IMPORTANT] Package manager for next release
Talking about package managers. What are the most extensive and most reliable site for slackware sources? I would like to use these to work with gslapt and maybe QTswaret.
Prendre son temps, profiter de celui qui passe.
Re: [IMPORTANT] Package manager for next release
Looks at http://www.slackware.com/getslack/
NjVFQzY2Rg==
Re: [IMPORTANT] Package manager for next release
I would go as far as to state we could still recycle Slax modules if necessary, or build app snap-ins--that is, similar to the iOS, we could have apps that one could download from one GUI application center from one location, that could be dragged to one folder, or placed there upon download, and deleted easily, with no mess of uninstalling it. It'd be better than deactivating modules, though that in and of itself ain't a bad idea.
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: [IMPORTANT] Package manager for next release
Thanks. Finally, I found what I was looking for in /usr/doc/slapt-get-0.10.2d/example.slapt-getrc.i386 that comes with a slapt-get package.Hamza wrote:Looks at http://www.slackware.com/getslack/
Code: Select all
# Working directory for local storage/cache.
WORKINGDIR=/var/slapt-get
# Exclude package names and expressions.
# To exclude pre and beta packages, add this to the exclude:
# [0-9\_\.\-]{1}pre[0-9\-\.\-]{1}
EXCLUDE=^aaa_elflibs,^devs,^glibc-.*,^kernel-.*,^udev,.*-[0-9]+dl$,x86_64
# Base url to directory with a PACKAGES.TXT.
# This can point to any release, ie: 9.0, 10.0, current, etc.
# You should really choose from an example mirror URI below.
# SOURCE=ftp://ftp.slackware.com/pub/slackware/slackware-13.0/:OFFICIAL
...
# Sources for the testing, extra, and pasture areas - if you use them.
# Edit the URI below for the Slackware version you're using.
# SOURCE=ftp://ftp.slackware.com/pub/slackware/slackware-13.0/extra/:PREFERRED
# SOURCE=ftp://ftp.slackware.com/pub/slackware/slackware-13.0/testing/
# SOURCE=ftp://ftp.slackware.com/pub/slackware/slackware-13.0/pasture/
...
# Slackware mirrors to choose from.
# Please use one of these in preference to ftp.slackware.com!
# SOURCE=http://slackware.oc9.org/slackware-13.0/:OFFICIAL
# SOURCE=http://slackware.mirrors.pair.com/slackware-13.0/:OFFICIAL
# SOURCE=http://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://darkstar.ist.utl.pt/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://download.sourceforge.net/pub/mirrors/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://ftp.planetmirror.com/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://gd.tuwien.ac.at/opsys/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://mirror.switch.ch/ftp/mirror/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://ncart.scs.ryerson.ca/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://slackware.oregonstate.edu/slackware-13.0/:OFFICIAL
# SOURCE=http://sunsite.cnlab-switch.ch/ftp/mirror/slackware/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://www.slackware.at/data/slackware-13.0/:OFFICIAL
# SOURCE=http://www.slackware.no/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://slackware.itsoft.at/slackware/slackware-13.0/:OFFICIAL
# SOURCE=http://www.slackware.org.uk/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://darkstar.ist.utl.pt/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://distro.ibiblio.org/pub/linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://dl.xs4all.nl/pub/mirror/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp-linux.cc.gatech.edu/pub/Linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.biochem.uthscsa.edu/pub/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.cerias.purdue.edu/pub/os/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.cs.columbia.edu/archives/os/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.edisontel.it/pub/Slackware_Mirror/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.etse.urv.es/pub/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.heanet.ie/mirrors/ftp.slackware.com/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.kreonet.re.kr/pub/Linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.linux.tucows.com/pub/distributions/Slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.loxinfo.co.th/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.mirror.ac.uk/sites/ftp.slackware.com/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.nluug.nl/pub/os/Linux/distr/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.physics.upatras.gr/mirror/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.planetmirror.com/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.rediris.es/mirror/linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.slackware-brasil.com.br/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.slackware.at/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.slackware.no/pub/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.slackwarebrasil.org/pub/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.sunet.se/pub/Linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.tau.ac.il/pub/OS/Slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.ulatina.ac.cr/Unix/Linux/Slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.unina.it/pub/linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.uniovi.es/pub/slackware/:OFFICIAL
# SOURCE=ftp://gd.tuwien.ac.at/opsys/linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://mirror.aarnet.edu.au/pub/slackware/slackware-current/:OFFICIAL
# SOURCE=ftp://mirror.pudas.net/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://mirror.switch.ch/mirror/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ncart.scs.ryerson.ca/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://sharon.esrac.ele.tue.nl/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://slackware.linux.no/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://slackware.oregonstate.edu/pub/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://sunsite.cnlab-switch.ch/mirror/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://sunsite.cnlab-switch.ch/mirror/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://sunsite.icm.edu.pl/pub/Linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://sunsite.pub.ro/pub/Linux/distributions/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://slackware.itsoft.at/slackware/slackware-13.0/:OFFICIAL
# SOURCE=ftp://ftp.slackware.org.uk/slackware/slackware-13.0/:OFFICIAL
# 3rd party sources.
# You can use multiple sources, such as linuxpackages.net, GSB or others; simply
# list a SOURCE for each you want to use. These are not recommended on
# production servers, but often provide good packages for desktop users.
# It is essential that you check the project websites for compatibility with
# your Slackware version before enabling any of these SOURCEs.
# See the README for more details.
#
# GNOME.SlackBuild (GSB) - http://gnomeslackbuild.org/
# SOURCE=http://www.slackware.org.uk/gsb/gsb-current/:CUSTOM
# SOURCE=ftp://ftp.slackware.org.uk/gsb/gsb-current/:CUSTOM
# SOURCE=ftp://ftp.slackware.pl/pub/gnomeslackbuild/gsb/gsb-current/:CUSTOM
# SOURCE=http://slackware.rol.ru/gsb/gsb/gsb-current/:CUSTOM
# SOURCE=http://get.gnomeslackbuild.org/gsb/gsb-current/:CUSTOM
#
# LinuxPackages - http://www.linuxpackages.net/
# SOURCE=http://ftp.naist.jp/pub/Linux/linuxpackages/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://slackware.rol.ru/linuxpackages/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://ftp.de-mirror.org/linuxpackages/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://linuxpackages.telecoms.bg/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://mirrors.unixsol.org/linuxpackages/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://lp.slackwaresupport.com/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://mirror.slackwarebrasil.org/linuxpackages/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://linuxpackages.inode.at/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://www.software-mirror.com/linuxpackages/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://linuxpackages.cs.utah.edu/Slackware/Slackware-12.2/:CUSTOM
# SOURCE=http://www2.linuxpackages.net/packages/Slackware/Slackware-12.2/:CUSTOM
#
# Other unofficial sources.
# SOURCE=http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-12.2/:CUSTOM
# SOURCE=ftp://ftp.gware.org/12.2/2.22.0/packages/:CUSTOM
# SOURCE=http://www.slackages.com/slapt-get/jlp/:CUSTOM
# SOURCE=http://www.slackages.com/slapt-get/jto/:CUSTOM
# SOURCE=http://trovao.droplinegnome.org/extras/:CUSTOM
# SOURCE=http://mirror.datapipe.net/norlug/mutagenix/packages/:CUSTOM
# SOURCE=http://www2.linuxpackages.net/packages/SlackBuilds/:CUSTOM
# SOURCE=http://slackpacks.rlworkman.net/12.2/:CUSTOM
# SOURCE=http://slackpacks.rlworkman.net/current/:CUSTOM
# SOURCE=http://www.slackware.com/~alien/slackbuilds/:CUSTOM
# SOURCE=http://download.zenwalk.org/i486/snapshot/:CUSTOM
# SOURCE=http://de.repos.slackware-current.net/:CUSTOM
# SOURCE=http://slackware.sukkology.net/repository/:CUSTOM
# SOURCE=http://www.tenboard.com/slackware/slackware-11.0/:CUSTOM
# SOURCE=http://shtrom.free.fr/slackware/slackware-10.1/:CUSTOM
# SOURCE=http://www.stabellini.net/filesystem/repository/Stefano_Stabellini:CUSTOM
Prendre son temps, profiter de celui qui passe.
Re: [IMPORTANT] Package manager for next release
If someone want post a log , you must use pastebin.com or something like that.
Please do not post a full log in the forum.
But , you can post the source code of a script.
@francois.e
Your last post with the code is allowed.
Please do not post a full log in the forum.
But , you can post the source code of a script.
@francois.e
Your last post with the code is allowed.
NjVFQzY2Rg==
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: [IMPORTANT] Package manager for next release
Thanks Hamza.
As we say in french: "je suis tres negotiable de toute maniere".
As we say in french: "je suis tres negotiable de toute maniere".
Prendre son temps, profiter de celui qui passe.
Re: [IMPORTANT] Package manager for next release
I agree with you
Mais , s'il vous plait , veuillez ne pas parlez français dans ce forum.
Mais , s'il vous plait , veuillez ne pas parlez français dans ce forum.
NjVFQzY2Rg==
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: [IMPORTANT] Package manager for next release
Sure.
But heading to a very important matter: How are we going to resolve the problem of package dependencies from one computer to another as they are going to have different set of modules or packages. Isn't a package manager like slakyd, looking on the computer for existing packages, is essential to resolve the problem of missing or extra dependencies? Remember this was a very big problem on slax.
I would like to hear wise persons on this topic. My simple package needs rules me out on this issue.
But heading to a very important matter: How are we going to resolve the problem of package dependencies from one computer to another as they are going to have different set of modules or packages. Isn't a package manager like slakyd, looking on the computer for existing packages, is essential to resolve the problem of missing or extra dependencies? Remember this was a very big problem on slax.
I would like to hear wise persons on this topic. My simple package needs rules me out on this issue.
Prendre son temps, profiter de celui qui passe.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: [IMPORTANT] Package manager for next release
I think the modules for Porteus should be screened and tested and have a dependency list in the var/log/packages file. These will be searched for as either already activated or residing in your chosen local modules folder. I think the 'libraries' section of the modules repo will be extensive. It may mean that module progress is slower, but i think it would be better to have modules that work reliably rather than hit and miss as in slax. So far this is only theory and i am happy to receive other ideas. I'd like to release next version of 32bit and then get started on package manager.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.