slackpkg++ : New Package management tool for Slackware (Under Development)

linuxxer · 06-03-2017, 09:58 AM

Slackers,

I am tring to implement new binary package management for Slackware.

The project is under developement (NOT complete yet).

I am sharing with you idea about my project.

I am tring to implement binary package manangement tool similar to slackpkg,
but to handle multiple repositories.

Some assumptions:
1. Each repository uses the uniq tag for package (except offical Slackware repository)
For example: xfce4-smartbookmark-plugin-0.4.5-x86_64-1_rlw
Tag is _rlw

2. For this tool all package must having configured repository (package sources) or package must be blacklist (not manage by this tool).

3. This tool not handle repository with any assign priority. If you install the package from any repository,
the using tag that package will be upgrade from same repository.

NOTE : Command line options is not implement yet.

Strict Syntax:
# slackpkg++ update

# slackpkg++ upgrade-all

# slackpkg++ install <repository_name> <pkg_name>

This is just working copy of my project (NOT a complete project)

I have implemented my idea about package management tool.
I like to know your suggestion for this project before completion (So that I can implement).
That is why I am sharing the code.

I have plan to implement ncurses base interface.

Please go through the shell script before doing anything.
I have tested code on my single machine (x86_64 bit).
This tool is run in debug.
This will not install/remove any packages.
Download the package verify it and output the command.
Download path : /var/cache/packages/

TO install run command :

Code:

sudo ./install-script

NOTE: RUN THIS CODE AT OWN RISK

Please check the link: https://sourceforge.net/projects/slackpkg-plus-plus/

I like to know your idea about package management.

Thanks.

55020 · 06-03-2017, 10:13 AM

Could you please consider changing the name? There's already a problem with slackpkgplus, newbies just call it 'slackpkg' and don't understand they are using something different and don't mention slackpkgplus when they ask for help. Having "slackpkg++" as well would make this problem much, much worse

montagdude · 06-03-2017, 04:07 PM

Just curious, because it sounds like the goal is pretty similar to slackpkgplus -- is there a difference?

Didier Spaier · 06-03-2017, 04:22 PM

Similar question, differences with slpkg?

rkelsen · 06-03-2017, 09:03 PM

Quote:

Originally Posted by linuxxer

I am tring to implement new binary package management for Slackware.

Whose repository will you use?

linuxxer · 06-03-2017, 10:29 PM

Quote:

Originally Posted by 55020

Could you please consider changing the name? There's already a problem with slackpkgplus, newbies just call it 'slackpkg' and don't understand they are using something different and don't mention slackpkgplus when they ask for help. Having "slackpkg++" as well would make this problem much, much worse

Like vi improved version is called vim, similarly this tool provide slackpkg similar functionality plus additional feature to handle 3rd party repository.
That is why I used this name.

linuxxer · 06-03-2017, 11:04 PM

Quote:

Originally Posted by montagdude

Just curious, because it sounds like the goal is pretty similar to slackpkgplus -- is there a difference?

My aim is to provide slackpkg similar functionality.
My tool is similar to slackpkg+ not to handle any repository with any assign priority.

It allow user to choose package and the repository. After that the will upgraded from the same repositoty.

linuxxer · 06-03-2017, 11:10 PM

Quote:

Originally Posted by Didier Spaier

Similar question, differences with slpkg?

I heard about slpkg (on this forum). It is very impressive. Handle package dependency automatically.

I dont belive in automatic dependency management. My allows to choose package and repository.

I have plan to implement template based dependency (NOT implementded yet).

I have plan to implement ncursed based interface (additional to command line) which made my tool easy to use.

linuxxer · 06-03-2017, 11:16 PM

Quote:

Originally Posted by rkelsen

Whose repository will you use?

I not very experienced person in Slackware.

I know few repositoires that I configured in this tool.

Code:

alienbob.cfg  microlinux.cfg  msb.cfg  rlworkman.cfg  slackonly.cfg  slackware.cfg

Currently these repositories are configured in my tool.

If you maintain Slackware similar repository format, then It will also work with my tool.

linuxxer · 08-03-2017, 11:45 AM

Slackers,

I am working on binary package management tool, similar to slackpkg.
This tool work with multiple package management repositories (package sources).

No automatic dependency management.
Not handle any package source (repository) with any assigned priority.

Now this tool provide minimal command line functionality.
I am working on Changelog option.

NOTE: Run this code at your own risk.

To compile:

Code:

make

To install:

Code:

sudo make install

To run:

Code:

./slackpkg++ --help

I have done little bit testing on Slackware current x86_64 bit system.
By default Slackware current 64 bit package sources are configured.
So you can change sources by editing files in /etc/slackpkg++/sources directory.

Need suggestions.

Download link: https://sourceforge.net/projects/slackpkg-plus-plus/

Happy Slacking...

ponce · 08-03-2017, 11:55 AM

hi linuxxer,

could you please remove my personal repository from the available sources of slackpkg++? Its use with any package manager is not supported at all.

thanks in advance.

linuxxer · 08-03-2017, 11:29 PM

@ponce: Ok Accepted

ChuangTzu · 08-04-2017, 02:59 PM

Quote:

Originally Posted by linuxxer

I not very experienced person in Slackware.

and therein lies the problem. why not become experienced with Slackware before reinventing a wheel that has been reinvented in multiples.

Drakeo · 08-04-2017, 07:26 PM

I love Eric's work. I donate a few times a year. we all should he needs the beer. but I have had little luck with his slackpackage plus. It is me I am sure I have set it up multiple times. but i guess I am just an edit.
I just do a rysnc to update what I want and install. i hope one day I become smart enough to run slackpkg pluss. and stop breaking things. I hope this new one here works different and is more simple.

Code:

# select your version of slackware to use
select 1 if 14.1 x86
select 2 if 14.1 x86_64
select 3 if 14.2  x86
select 4 if 14.2  x86_64
select 5 if current x86
select 6 if current x86_64
# multilib for your version
select m1 if 14.1
select m2 if 14.2  
select m3 if current 
# select types of software r repositories and rss with restricted
select  r-14.1     14.1
select  rrs-14.1   14.1
select  r-14.2     14.2 
select  rrs-14.2   14.2 
select r-current   current 
select rrs-current  current 
# for ktown same thing.

I know his configs looks easy when I see his scripts.
I break it for some reason. so I just rysnc the stuff that goes into it and upgradepkg --install-new *.t?z
now my stuff never breaks.
I had a dime for evertime i screwed slackpkgplus up and faild to down load the stuff and install
I would be rich.
Remember it is operator failure on my end.
as for this new one oh well wait to see the configs.

linuxxer · 08-05-2017, 12:13 AM

Quote:

Originally Posted by ChuangTzu

and therein lies the problem. why not become experienced with Slackware before reinventing a wheel that has been reinvented in multiples.

Currently I am just learning how to develop code on Slackware Linux.

Programming is my hobby. That is reason I am working on this project.

As I said, this can be another alternative project (like other project) for Slackware.

I like to know how you and another Slackware Users do the package management with multiple repository.

I know about slackpkg+. I like to know other tools you use.

Thanks for reply.

Happy Slacking...