To install or remove something, sure.. but if all you want to do is look through the package database, it really should be able to do so without becoming superuser. I personally just open up a text editor to the appropriate file in /var/log/packages, but YMMV.

MysticalGroovy: perhaps you can think about using src2pkg as a backend for the .deb and .rpm conversions, since it's gained a lot of knowledge on how to make sure the conversion creates a valid package with files conforming to Slackware conventions.

@tommcd:
probably not in the next few months m8, I currently not have the time or the knowledge to port Slackpack to 64bit slackware
Ill add it as a feature request on Slackpack sourceforge site so i wont forget it

@mostlyharmless
Slackpack 1.1.5 is written on Qt4, so the latest Slackware 13.0(using KDE4/Qt4) is required to run Slackpack 1.1.5, theoretically speaking Slackpack 1.1.5 could run on an oldest version of Slackware if you have Qt4.5 installed.

@bgeddy:
currently you cannot use regular expressions on the search box but ill add it as a feature request in sourceforge project site so i wont forget to implement to the next slackpack release
(btw the search box is currently a bit beta as a feature)

thank you all for your answers ,
recently I got an email and a nice fellow called mr. Robby Workmanwho contributed alot to the Slackware community and he suggested me to add a source code control system for Slackpack, so basically Im working on it right now Ill post here for updates

@tuxdev,

hmm why not, thx for the suggestion

Ok i will test it this afternoon, but it, should be easy if it ask (graphically) for root password and load.

You're completely right. I was talking about the installation and remove part of the process.

Works fine using kdesu, thank you very much for your hard work

Yes - I agree with this. The application could check if the user is root when he requests an operation requiring root privileges or perhaps disable such options when the user is not root. As it is the app checks on entry for root status and exits if not found.
@MysticalGroovy : I know this may be a pain but the above mentioned functionality change would be very useful. It's nice to be able to browse packages as a normal user.

@bgeddy:

good morning m8
yeah i think it should be possible to browse the packages without becoming a superuser and i can implement it too in Slackpack, but do you really think its necessary?

I mean that the usage of a package manager is to update/install/remove etc packages from the system, to do this in slackware you need root access, if you cant get root access why do you want to use Slackpack for? you wont be able to process packages, you'll be able to only see the installed packages on the system, and if you cant process the installed packages, why you would want to..see them?

p.s: sry for my bad english btw

ok, mr Robby Workman just confirmed that Slackpack builds and runs fine on x86_64 so it doesn't need no porting at all

@MysticalGroovy: Thanks for the quick reply. Your English is great BTW - no problems !
This is possibly me just being lazy. I always operate as a normal user (not root) and don't like going to root unless neccesary. I'm used to using Kpackage in KDE3 which allows me to browse the installed packages list and look at what files are in a package without being root. In that application it's not till I want to do something that needs root privileges that I have to give the root password.
This is just a small observation and not really a "make or break" aspect of the application - just a little convenience.
I'm really appreciative of your work on this and think the application is great ! Good work.

not a bad idea!
I should implement a feature where the user will be able to see files in the selected package like in KPackage! (yes, without being root )

thx bgeddy !

btw gentlemen, i would like to ask you if you have any feature request you should add them here:
http://sourceforge.net/tracker/?func...9&atid=1031794
so i wont forget them

Good work! It's nice to have a GUI sometimes and my wife will be glad she doesn't have to mess with that "text thingy" anymore.

I downloaded the source, and after editing the makefile, I recompiled the source to work in Slackware64. That said, it has no package afterwards to install. However, I can run the binary in the bin directory using kdesu. It came up clean and seems ready to go. The app looks very nice with a straightforward ui that is very user friendly.

I'm going to create a menu entry to make it easier to call up by kdesu. I sure wish I knew more on how to write code!

Thanks, MysticalGroovy - well done!

I downloaded the source, and after editing the makefile, I recompiled the source to work in Slackware64. That said, it has no package afterwards to install. However, I can run the binary in the bin directory using kdesu. It came up clean and seems ready to go. The app looks very nice with a straightforward ui that is very user friendly.

I'm going to create a menu entry to make it easier to call up by kdesu. I sure wish I knew more on how to write code!

Thanks, MysticalGroovy - well done!

I have included the makefile for others to see and comment.

Attached Files

Makefile.txt (9.0 KB, 21 views)