slackyd: a simple but efficient package manager
Re: slakyd: a simple but efficient package manager
hi fanthom:http://slacky.eu/~dani/slackyd/sources/ ... .0.tar.bz2
Posted after 1 minute 12 seconds:
the link is dead but today have been released the slackyd that support 13.37 slackyd v1.0
Posted after 1 minute 12 seconds:
the link is dead but today have been released the slackyd that support 13.37 slackyd v1.0
- 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: slakyd: a simple but efficient package manager
1)Slackyd is a great tool. However, it would be great to make it very efficient by selecting sources and repertories that could bring as great a number of packages without having to resort to google. Do you have a selection of repertories and of sources that would cover broadly the userland of slackware. What would be your receipe or your selection? (Could you make it fit in the file:///etc/slackyd/slackyd.conf and post it on this thread)
2) In addition, maybe we could have links to packages that are not common on slackware.com or most common repertories on some site of our own, thus creating our favorite source of packages. This would be a good thing because we could this way accept packages that are problem free for porteus this way.
3) These issues are interesting as brokenman is working on a gui script that converts directly from slackyd packages into modules compatible with porteus:
http://forum.porteus.org/viewtopic.php?f=39&t=373
So improving the sources would improve its package manager.
4) What is also interesting is that we could use the same extended sources for slackyd for slapt-get and its front end gslapt. Slapt-get has a resolution of dependencies thru Stabellini's repertory, see:
http://forum.porteus.org/viewtopic.php?f=53&t=115
2) In addition, maybe we could have links to packages that are not common on slackware.com or most common repertories on some site of our own, thus creating our favorite source of packages. This would be a good thing because we could this way accept packages that are problem free for porteus this way.
3) These issues are interesting as brokenman is working on a gui script that converts directly from slackyd packages into modules compatible with porteus:
http://forum.porteus.org/viewtopic.php?f=39&t=373
So improving the sources would improve its package manager.
4) What is also interesting is that we could use the same extended sources for slackyd for slapt-get and its front end gslapt. Slapt-get has a resolution of dependencies thru Stabellini's repertory, see:
http://forum.porteus.org/viewtopic.php?f=53&t=115
Last edited by francois on 05 May 2011, 15:54, edited 1 time in total.
Prendre son temps, profiter de celui qui passe.
- Tonio
- Contributor
- Posts: 276
- Joined: 28 Dec 2010, 16:37
- Distribution: Slackware,porteus,FreeBSD,Slax
- Location: 127.0.0.1
Re: slakyd: a simple but efficient package manager
I don't know if this is relevant in this thread, but I will post here. Tomas M slax creator has dissected the Slackware 13.37 release and deps:
http://www.tomas-m.com/blog/upload/slac ... -13.37.php
I was reading the Slackware Handbook, in there I read that Slackware is a system which is not meant to have dependency checking:
http://www.slackbook.org/html/package-management.html
``The truth about pkgtool is not that it doesn't exist, but that it doesn't do any dependency checking.
Apparently many people in the Linux community think that a packager manager must by definition include dependency checking. Well, that simply isn't the case, as Slackware most certainly does not. This is not to say that Slackware packages don't have dependencies, but rather that its package manager doesn't check for them. Dependency management is left up to the sysadmin, and that's the way we like it.''
I learned more about Slackware updating via a Distrowatch weekly:
http://distrowatch.com/weekly.php?issue=20090518
# slackpkg update
# Install new packages:
# slackpkg install-new
# Upgrade all installed packages:
# slackpkg upgrade-all
added:
[olivares@grullahighschool ~]$ date +%Y%m%d
20110505
[olivares@grullahighschool ~]$ uname -m
amd64
I setup a script that checks for new packages and installs them via slackpkg. I am happy to run Slackware-current.
http://www.tomas-m.com/blog/upload/slac ... -13.37.php
I was reading the Slackware Handbook, in there I read that Slackware is a system which is not meant to have dependency checking:
http://www.slackbook.org/html/package-management.html
``The truth about pkgtool is not that it doesn't exist, but that it doesn't do any dependency checking.
Apparently many people in the Linux community think that a packager manager must by definition include dependency checking. Well, that simply isn't the case, as Slackware most certainly does not. This is not to say that Slackware packages don't have dependencies, but rather that its package manager doesn't check for them. Dependency management is left up to the sysadmin, and that's the way we like it.''
I learned more about Slackware updating via a Distrowatch weekly:
http://distrowatch.com/weekly.php?issue=20090518
# slackpkg update
# Install new packages:
# slackpkg install-new
# Upgrade all installed packages:
# slackpkg upgrade-all
added:
[olivares@grullahighschool ~]$ date +%Y%m%d
20110505
[olivares@grullahighschool ~]$ uname -m
amd64
I setup a script that checks for new packages and installs them via slackpkg. I am happy to run Slackware-current.
Last edited by Tonio on 05 May 2011, 15:19, edited 1 time in total.
Re: slakyd: a simple but efficient package manager
Yes, Slackware package manager do not know regarging depencies of packages
Messing with depencies checking go over sysadmin - e.g user
Messing with depencies checking go over sysadmin - e.g user
- Tonio
- Contributor
- Posts: 276
- Joined: 28 Dec 2010, 16:37
- Distribution: Slackware,porteus,FreeBSD,Slax
- Location: 127.0.0.1
Re: slakyd: a simple but efficient package manager
That is the slackware way There are several apps to help in updating. I like the concept of the (PIG) Port Install Gui from kongoni. This is very similar to the ports system used in FreeBSD. Your deps are taken care for you Here as for porteus, I like it the way it is. If I want a certain package, I check the modules available, if I don't find any, I build my own from source and track down dependencies on my own. Several times, it may take a while, but I am ok with it.Falcony wrote:Yes, Slackware package manager do not know regarging depencies of packages
Messing with depencies checking go over sysadmin - e.g user
Re: slakyd: a simple but efficient package manager
an user of slackyd.eu have build a firefox add on that search package of slackware there is 4 repository 32 and 64 bit and slackware version 12.1 to current the adds on work well with the firefox 4.0 version,ytake a look if you want.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: slakyd: a simple but efficient package manager
@beny
sounds interesting
could you provide a link to it?
sounds interesting
could you provide a link to it?
Please add [Solved] to your thread title if the solution was found.
Re: slakyd: a simple but efficient package manager
Posted after 16 minutes 23 seconds:
https://addons.mozilla.org/en-US/firefo ... search-ba/
i have posted the old link,this is the good one
https://addons.mozilla.org/en-US/firefo ... search-ba/
i have posted the old link,this is the good one
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: slakyd: a simple but efficient package manager
@beny
nice one, but takes too much space on the bar when activated
i will add it to the firefox module but it wont be enabled by default.
Cheers
nice one, but takes too much space on the bar when activated
i will add it to the firefox module but it wont be enabled by default.
Cheers
Please add [Solved] to your thread title if the solution was found.
Re: slakyd: a simple but efficient package manager
Slackyd is a great tool. But it does not give sizes of packages it is going to download. Is there any way to know the sizes? Also, can we save the list of required packages to download them later ?
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: slakyd: a simple but efficient package manager
Is there any way to know the sizes?
Slackyd keeps the index files cached at: /var/slackyd (unless you changed it). have a hunt around in there for the PACKAGES.TXT files. There should be a couple. You can grep them for the compressed package size. Something like:
Slackyd keeps the index files cached at: /var/slackyd (unless you changed it). have a hunt around in there for the PACKAGES.TXT files. There should be a couple. You can grep them for the compressed package size. Something like:
Code: Select all
PTH=/var/slackyd/slackware/PACKAGES.TXT
grep -A3 "NAME: yourpackagename" $PTH | tail -n1
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.
Re: slakyd: a simple but efficient package manager
On my system, 'slackyd -d' command detected 43 missing libraries, but only one downloadable package; packages for other libraries were not found. How do I manage this ?
- Ahau
- King of Docs
- Posts: 1331
- Joined: 28 Dec 2010, 15:18
- Distribution: LXDE & Xfce 32/64-bit
- Location: USA
Re: slakyd: a simple but efficient package manager
there are two or three unresolved dependencies in standard Porteus. Mine shows libruby, libnotify, and libQtCore. The rest that you see are probably from modules you've installed (especially if you've converted slax modules for use, as they were built for a much older system, and slax modules don't have a good way to resolve dependencies).
If you run slackyd -d again, you can scroll up to where it says "Found 43 missing dependencies". Each missing library shows what package it is required by (and what file inside that package requires it), so you should be able to track down which module is to blame for your missing deps. It's a tedious process, and that's why brokenman is working on a better system for us, with higher quality modules and dependency resolution
If you run slackyd -d again, you can scroll up to where it says "Found 43 missing dependencies". Each missing library shows what package it is required by (and what file inside that package requires it), so you should be able to track down which module is to blame for your missing deps. It's a tedious process, and that's why brokenman is working on a better system for us, with higher quality modules and dependency resolution
Please take a look at our online documentation, here. Suggestions are welcome!
Re: slakyd: a simple but efficient package manager
If I need a library and it is not available with slackyd, I need to find the source of library from its web page and compile it myself. Is that correct ?