LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-03-2017, 04:30 PM   #1
lotar
LQ Newbie
 
Registered: Aug 2012
Location: Rome
Distribution: Slackware -current
Posts: 4

Rep: Reputation: 14
SlackMan - Slackware Package Manager project


Hi Slackers,
i'm happy to announce a new project called "SlackMan" (aka Slackware Package Manager). SlackMan is a wrapper of pkgtools (such as slackpkg, slapt-get, etc) that provides an easy-to-use interface for install, upgrade and monitoring new ChangeLogs and Security Fix from officials and third-party repository.

SlackMan features:
  • Written in Perl (5.10) and compatible from Slackware 12.2 to latest (14.2 and -current)
  • Multiple repository support (official and third-party)
  • Use SQLite database to store all repository metadata (Packages, ChangeLogs, etc.) and speedup upgrade package calculation
  • Support package dependency resolution (if the repository have this support)
  • Bash completion support
  • Is integrated with PolicyKit and D-Bus (via org.lotarproject.SlackMan interface)
  • Include a desktop client that notify (via org.freedesktop.Notifications) package upgrade, ChangeLogs and Security Fix (see the attachments)

Actually support this repository:
  • Official Slackware stable and -current
  • SlackOnly (SlackBuilds.Org recompiled SlackBuilds)
  • Slackers (Conraid)
  • Slacky (Italian Slackware Community)
  • AlienBob (plus restricted repository)
  • Robby Workman
  • ktown (KDE5)
  • Cinnamon SlackBuilds
  • MATE SlackBuilds
  • Salix
  • Microlinux

This is a few examples

This is a possible procedure to upgrade, install new packages and remove obsolete packages from Slackware repository:

Code:
slackman update
slackman upgrade --repo slackware
slackman install --new-packages --repo slackware
slackman remove --obsolete-packages
Display a ChangeLogs:

Code:
slackman changelog --repo slackware:packages
Upgrade packages excluding kernel packages:

Code:
slackman upgrade --exclude kernel-*
For more information about SlackMan see https://lotarproject.github.io/slackman/

I hope this is helpful,
Joseph
Attached Thumbnails
Click image for larger version

Name:	dbus-notification-upgraded-packages.png
Views:	120
Size:	10.3 KB
ID:	26031   Click image for larger version

Name:	dbus-notification-slackware-upgrade.png
Views:	97
Size:	11.1 KB
ID:	26032   Click image for larger version

Name:	dbus-notification-slackware-security.png
Views:	114
Size:	21.8 KB
ID:	26033   Click image for larger version

Name:	dbus-notification-slackware-changelog.png
Views:	142
Size:	22.8 KB
ID:	26034  
 
Old 10-05-2017, 08:40 AM   #2
slackb0t
Member
 
Registered: Apr 2005
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 238

Rep: Reputation: 56
It looks interesting. Package management is usually a hot topic around here, I am surprised there aren't more comments with 500 views.
 
2 members found this post helpful.
Old 10-06-2017, 01:54 AM   #3
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 2,741

Rep: Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161Reputation: 1161
Quote:
Originally Posted by slackb0t View Post
It looks interesting. Package management is usually a hot topic around here, I am surprised there aren't more comments with 500 views.
Meh.
 
4 members found this post helpful.
Old 10-07-2017, 04:42 PM   #4
ChuangTzu
Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix, FreeBSD, openSUSE, Debian
Posts: 466

Rep: Reputation: 347Reputation: 347Reputation: 347Reputation: 347
Lots of package managers for Slackware, including its own. Why the need to constantly reinvent the wheel? I would suspect this is why you see more views then comments.
 
1 members found this post helpful.
Old 10-10-2017, 05:29 AM   #5
GazL
Senior Member
 
Registered: May 2008
Posts: 4,485
Blog Entries: 7

Rep: Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967Reputation: 1967
A little competition for slackpkg doesn't seem like a bad thing to me. Maybe this is better, maybe not.
Having said that, I don't use slackpkg either so this isn't for me, but kudos to it's author non the less.

I think the biggest issue you're going to have with adoption is all the extra perl modules required to run it. When you're coming with an alternative to an established tool you're going to have to get over people's inertia, and having them have to go and install several perl modules isn't going to help with that.

Best of luck with your project.
 
4 members found this post helpful.
Old 10-10-2017, 06:40 AM   #6
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,574
Blog Entries: 56

Rep: Reputation: Disabled
I'm satisfied with slackpkg and sbopkg + queuefiles; but good luck, anyway.
 
1 members found this post helpful.
Old 10-10-2017, 01:07 PM   #7
Slax-Dude
Member
 
Registered: Mar 2006
Location: Valadares, Portugal
Distribution: Slackware
Posts: 412

Rep: Reputation: 152Reputation: 152
This tool is made with Perl.
It also requires some extra Perl modules to work.
The website tells me to either use sbopkg or look for them in slackbuilds.org (I could not find "http::tiny" and can't be bothered to install sbopkg) and some of them have dependencies as well.
It would help a lot if the packages required were available on the website.
 
1 members found this post helpful.
Old 10-10-2017, 01:27 PM   #8
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,427

Rep: Reputation: 610Reputation: 610Reputation: 610Reputation: 610Reputation: 610Reputation: 610
Quote:
Originally Posted by ChuangTzu View Post
Lots of package managers for Slackware, including its own. Why the need to constantly reinvent the wheel? I would suspect this is why you see more views then comments.
because obviously there is no solution that fits all needs and/or flavors, and if you are a developer and you are looking for some task to practice some development, it is a possible challenge / target if you sitting on a Slackware machine.
So it is not always just to create a tool, its often also a way for a developer to do some coding.
And who knows what interesting spin offs, often you will not see them because they will live an extra life, are coming out of such coding tasks
 
7 members found this post helpful.
Old 10-11-2017, 06:21 AM   #9
lotar
LQ Newbie
 
Registered: Aug 2012
Location: Rome
Distribution: Slackware -current
Posts: 4

Original Poster
Rep: Reputation: 14
Quote:
Originally Posted by Slax-Dude View Post
This tool is made with Perl.
It also requires some extra Perl modules to work.
The website tells me to either use sbopkg or look for them in slackbuilds.org (I could not find "http::tiny" and can't be bothered to install sbopkg) and some of them have dependencies as well.
It would help a lot if the packages required were available on the website.
Thanks for your interesting. I'm work to create a package (eg. slackman-perl-libs) with all required Perl modules for SlackMan for all supported Slackware release.
 
2 members found this post helpful.
Old 10-11-2017, 06:38 AM   #10
YesItsMe
Member
 
Registered: Oct 2014
Distribution: Void
Posts: 130

Rep: Reputation: 38
If anyone is interested in a rebuild of SlackMan in a statically compiled language (Common Lisp, C/C++ or something) to work around the Perl module dependency thing, I'd willingly join.
 
3 members found this post helpful.
Old 10-11-2017, 03:27 PM   #11
kevison
Member
 
Registered: Dec 2007
Location: Grand Rapids, Michigan USA
Distribution: Slack 14.2 64bit/32bit(current)
Posts: 127

Rep: Reputation: Disabled
IMHO ... Package managers are at the mercy of the distribution it seems... until the linux community comes to an agreeable consensus, we are stuck with a lots of different ways to install packages. I dream of a day when a standard comes out of all of this...
 
Old 10-11-2017, 11:48 PM   #12
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,023

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Quote:
Originally Posted by kevison View Post
I dream of a day when a standard comes out of all of this...
No chance.

https://imgs.xkcd.com/comics/standards.png
 
3 members found this post helpful.
Old 10-12-2017, 06:04 AM   #13
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware, *BSD
Posts: 396

Rep: Reputation: 470Reputation: 470Reputation: 470Reputation: 470Reputation: 470
Quote:
Originally Posted by kevison
until the linux community comes to an agreeable consensus
Or until somebody forces a new package management system on everybody else, by making everything dependent on it? Like what's happening with a software called <self-censored>. Wait, I can already hear the grisly «Software Center» marketing buzzword threatening the community. NOOOOOOooooo....

I have always thought that what makes the Linux ecosystem really interesting is its inherent diversity, not the attempts to turn it into a monoculture.

 
3 members found this post helpful.
Old 10-12-2017, 08:42 AM   #14
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,765

Rep: Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691Reputation: 2691
Just wondering: are these the same people who praise Slackware for its genuine and powerful albeit simple package management without automatic dependencies resolution and this notwithstanding reinvent a new package manager with automatic dependencies resolution every month?

Just curious...

Me, I am happy with slapt-get and gslapt on top of the Slackware tools
 
2 members found this post helpful.
Old 10-12-2017, 09:01 AM   #15
ChuangTzu
Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix, FreeBSD, openSUSE, Debian
Posts: 466

Rep: Reputation: 347Reputation: 347Reputation: 347Reputation: 347
Quote:
Originally Posted by a4z View Post
because obviously there is no solution that fits all needs and/or flavors, and if you are a developer and you are looking for some task to practice some development, it is a possible challenge / target if you sitting on a Slackware machine.
So it is not always just to create a tool, its often also a way for a developer to do some coding.
And who knows what interesting spin offs, often you will not see them because they will live an extra life, are coming out of such coding tasks
no problems there, people could also contribute to current projects.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware Package Manager hilario Slackware 10 08-16-2009 12:37 AM
Slackware package manager arnuld Slackware 7 05-03-2007 03:15 PM
Slackware package manager blood_omen Slackware 11 04-26-2004 05:49 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration