Slackers,

I am trying to create Package Management Tool for Slackware -- named "slackpack".

I am comparatively NEW to the Slackware.

I am trying to create a tool which work with Slackware repository
and **SLACKWARE SIMILAR BINARY PACKAGE REPOSITORIES**.

AIM : NOT TO HANDLE ANY REPOSITORY WITH ANY ASSIGNED PRIORITY

Details are provided in attached README.TXT file.

Kindly check the attach files for more information and source code.

Suggestions are expected.

Thanks in advance.

Attached Files

	README.TXT (6.6 KB, 57 views)
	slackpack-testing.tgz.txt (12.6 KB, 33 views)

Hi linuxxer,

I can't say much as I am not proficient in C.

IMO a -h or --help option stating the options and usage is necessary (as when you type "slackpkg" or "installpkg" without arguments, for instance).

I can hardly understand how to use it reading README.TXT, maybe that's because English is not my native language.

So, how much do you know about binary compatibility?

1 members found this post helpful.

I think he was not referring to binary compatibility, but rather he wants to support 3rd party Slackware package repositories with a layout and metafiles similar to the official Slackware repository.

Eric

Well, Eric, of course binary compatibility comes into play -even the official repos are sorted by architecture and using packages from other repos is 'frowned on', if for no other reason than possible compatibility problems. It seems obvious that he must know something about what packages might be compatible with which versions, but I'm not wanting to argue about it.

I would point out though that the name 'slackpack' is already used by another project -in fact by more than one:
http://sotirov-bg.net/slackpack/
http://sourceforge.net/projects/slack-pack/

@Didier Spaier
This tool is under-developement. It is just an idea.
So I developed only sufficient required functionality.
Once everything get finalised after that I will implement all required command-line options.

It is very difficult to modify C code.

English is also not my native language.

Thanks for your reply.

@gnashley
If your talking about system architecture related package compatibility,
then package having arch information in package tarball name.

If you talking about package compatibility with Slackware version.
that I want to know from experienced Slackware users like you.

I already mentioned that I am comparatively new to Slackware.

I per my understanding.

Slackware 13.37 package may not work with Slackware 14.0.
But I think Slackware-Current packages work on installed Slackware 14.0.

When new Slackware version get released,
Slackware-current is further developement of that version, for next Slackware stable release.

If I am wrong, then please correct me.
For tool developement, this is also very important for me.
I just forgot to mention this (package compatibility) point in README.TXT file.

Thanks for url.
I will find new name for my tool.

Thanks for your reply.

Edited:
gnome-slackbuilds13.37 repository is configured,
because for testing I need more repositories, which having Slackware similar repository structure.


@Alien Bob
Thanks for your reply.
Any suggestions?

There is no guarantee on this. With Slackware-current you see package additions, package removals, upgrades to glibc, new X versions, etc that all could lead to problems with packages that work on Slackware 14.0.

@linuxxer,
the more tools there are the more joice exist.
and I am also a fan of writing tools, even if something simmilar may already exists, there is always the chance that new software does something additional, better or becomes something different,
but let me ask, do you know slapt-get , http://software.jaos.org/
I do not use it on Slackware, but Salix uses it , and it seems to me that it has the features you mentioned.

I tried slapt-get, It is great.
I am writting this tool just for fun.
Just my own implementation.

1 members found this post helpful.

I agree with you.

But somebody wants to install FEW packages from slackware-current, then it is allowed by tool.
Installing packages will be sysadmin's responsibility.

I know slackware-current is rolling release distribution.

Aim : Implement slackpkg similar functionality + Handling multiple binary repositories.

1 members found this post helpful.

any updates??

1 members found this post helpful.

Slackpkg is very simple, it can only do basic job, job one can really do easy without it. I don't think there is need for similar application.

If you really need some fun learn how slackpkg is creating templates. It will be very usefull to have applications able to generates templates you can feed slackpkg with. Say template for small installation, medium, huge, full, desktop, server, vm host, etc.

1 members found this post helpful.