all these files are included and distributed in the .tgz slackpack package,
i just included them in the source, there's no installation script to fully install slackpack with the icons and stuff yet.

if you just want use Slackpack get latest .tgz package from:
http://slackpackpkgman.wordpress.com/download/

however its in my plans to include an installation script along with the source-code package.

Slackpack 1.1.8 version released :)

Updates:

* added preferences dialog (options for create package and convert package features
- now you can use src2pkg to convert packages as well :)
* you can now run slackpack as a normal user but root-only features are disabled.
* console output at list packages tab fixes
* code cleaned, removed old unused part of the code plus some unused includes
* added install section on generated Makefile (qmake)

Slackpack 1.1.8 package (.tgz)
Slackpack 1.1.8 source package (.tar.gz)
Slackpack Homepage

P.S:@tuxDev, please contact me to tell me where inside Slackpack to leave some credits for using src2pkg ;)

there is a problem in install script:
make install try to strip deb2tgz that is a bash shell script.


My workaround to solve is to add "QMAKE_STRIP = echo" into Slackpack.pro

arg!!! I hate it when im in hurry to release a new version and ignore errors like that...

anywayz fixed @current. thx zerouno

Thanx.

then, in version 1.1.8, the tgz have files that are not in source (all files outside /usr/share/slackpack as slackpack.desktop and others).
These file are presents in 1.1.4 source package, so I must to do:

# cd 1.1.4-source
# make install-data prefix=/
# cd 1.1.8-source
# make install

to build a complete 1.1.8 installation.

Goodbye,
01

well you actually have a complete 1.1.8 installation without copying any data from previous versions, the only that's missing from the source is the candy part of .desktop files and such which they're not necessary in the source side of things.

Hi MysticalGroovy, thanks for sharing your tool. Slackpack v1.1.8 compiled without errors and really improved a lot. Any plan to add support for translations? I played a little with 1.1.5 files and it was almost 85% translated =]

hmm a translation, not a bad idea,
I remember at ver1.1.5 i was trying to include a greek translation with Slackpack but i didnt give it alot of attention at that time.

the next ver of Slackpack will come with a greek translation and a template for translating slackpack to other languages too :)

Hey all,
i have a question, recently ive been using Slax as my pocket OS for my usbpen-drive, ive also created a slackpack Slax module..

do you think its a good idea to add slax related features to Slackpack? like slackware linux packages convertion to SLax modules and such.. or to leave Slackpack a slackware-only package manager?

thank you

Hello!
I use an usbpen-drive too. I find it very useful.
I tried Slax and NimbleX. Both use LZM modules.
In my opinion (if the proposal is still valid) I think its a very good idea. Do it! :)
Anyway Slackpack it's very helpful for me.
Good luck!

PS: sorry for my bad english... I am a beginner. :D

Gabriel

well Slax didnt work for me in the end, it seems its very unstable
ive tried it on 5pc's and im not really happy with it.
however ill continue to make .lzm modules for Slax users using tgz2lzm Slax convertion script.

Hello

First of all good job to the developers.Slackpack is very impressive.But i have some questions.

1)How can i install it?(I have notice that in the bin folder of the extract file there is the slackpack,with which i can run the program but what else must i do so the installation will be 100% completed...

2)What repositories does it use?

3)If i choose to install something,the slackpack will install the dependencies of the program automatic or i have to do it manually.

That's all for now :)

Hi and thanks for your answer,

EDITED
If you choose not to use the .tgz package there's an install section on the Makefile of Slackpack 1.1.8, run "make install" after compiling the source to install Slackpack.

about your second question, if understand it correctly you're asking what repo's does slackpack use to download packages? the answer is none, slackpack doesnt have that kind of feature in its stable release yet but a "get packages" feature is currently under development at -current

and about your third question, manually but when i finish writing the "Get Packages" feature, ill start writing an automatic dependencies installation option.

This is an excellent ideea. I think more people need such a package manager like this. Good luck! PS: I will be with an eye on you! ;)

Slackpack version 1.1.9 just released including a get packages feature! :)

Updates:

• added get packages feature (Download slackware linux packages from packages repositories)
• added translations support + greek translation
• Various bug fixes + code tweaks

Slackpack 1.1.9 package (.tgz)
Slackpack 1.1.9 source (.tar.gz)
------------------------
Slackpack Package Manager home

Ive noticed that Get Packages feature is abit slow and buggy sometime but its the first time Ive implemented something like this so please judge it wisely.

thank you :)

Your package manager is awesome, but just one thing. Is there any way to edit the repositories (i.e. the url of the repo). Right now it's just add or delete them.

edit: I also just noticed that if you have a - in the url of your repo, it treats it as a /
I have my personal repo which is
and it shows up as

no you cant edit the repo yet, but i can make it happen in the next version, also about the "-" on the repo links, I think i know whats happening here, try adding your repo url (it'll see "/" as "-") and see if you can access your repo with Slackpack and download some packages.

if not please reply so i can fix it :)

Nope, I tried to use a / instead and it still didn't work. I'm guessing that this:
snippet from getpackages.cpp is what is doing it. I tried switching the / and - and even commenting out the repositoryName.replace("/","-") line. Still no dice.

well Im not having the code infront of me right now but as you can see from the comment the "repositoryName" code snippet you show me above is used to create a valid file name for the package list Slackpack creates from the repositories in "${HOME}/.config/Slackpack"

for example if you have 2 repositories named

"http://testRepo1.org"
"ftp://testRepo2.com/pkgs/wh00t/"

each, on the repository list and then update the packages lists, in directory "${HOME}/.config/Slackpack" you should have two files named:

"http:--testRepo1.org"
"ftp:--testRepo2.com-pkgs-wh00t-"

each. This method is used because you cannot have an "/" on a file name.

so basically if you change the code you show me above Slackpack wont be able to read, (and maybe not even create) the package list file.

However tomorrow I'll try to work this issue out and release a fix :)

Good morning,

ahh man It'll sound a bit strange, but when im trying to add your repository "http://192.168.2.6/slackware/slackware64-13.0/slackware64/" and some other repo's with "-" inside the URL's Slackpack sees them correctly and doesnt convert anything to "/"!

lol? the official Slackware repository has some "-"'s inside its URL but I can see it and access it perfectly from Slackpack...

That is kinda strange. I tried the default repo as well as mine and it did the same thing.

try to download something from the official repo :)

I tried that, but got the same thing. Here is a screenshot.
And here is my ~/.config/Slackpack/repositories.conf

aa.. did you pressed the "Update Package List" button? :P

Yeah, that's when the error popped up. It does it any time I try to go to another tab and then back, or update the package list.

hmmmm are you running Slackpack as root?, if not try "su slackpack" and then update the package list and try to download a package

(btw what desktop environment are you running? not a problem-related question its just Slackpack looks abit strange, xfce maybe? hehe)

I'm using sudo to run it, I'll try as regular root. I'm using kde.

edit: Tried running it as root and I didn't get the error, but it doesn't update from the repo.

edit 2: Got it to work. I just omitted the /slackware64 at the end of the url and it worked. Are you planning on showing the available pkgs in the repo?

Hey and thanks for your reply, glad to here you got it working ;)

Well I was thinking to make Slackpack list all the available packets of the repositories in the repository list but this would cause a big pause if you have alot of repo's in the list, anyways I havent really decided if to do it or not, maybe I should give an option, lets say a "List Packages" button?

Another way, maybe have a sort of drop down menu that lets you choose which repo you want to list packages from?

hmm sounds cool too ;)

It can be set manually... if i remember :)

@MysticalGroovy

Please consider renaming Slackpack.

1. Slack is not a prefix you should be using, it should be reserved for official Slackware software.
2. Even if you were right to use the Slack prefix, I think Slackpack is distastefully close to Slackpkg, the official pkgtools wrapper included in Slackware.

well there are hundreds of projects using "slack" in their names out there and they are not in the official Slackware project, why should `Slackpack` has a problem with it?

however I will try contacting Pat and see if he has a problem with it :)

@ zordrak: You do realize that the whole "slack" thing comes from the Church of the Subgenius, right? I think MysticalGroovy is well within his/her right to use the word slack.

Bottom line is, have you run it past Pat? It would seem more than reasonable to do so.

yeap i did, he has no problem using the prefix "slack" in my application, because its not a linux distro, only an app for slackware linux... Pat also forwared my email to Piter Punk (the guy that codded slackpkg) to get his opinion about the name too.

Ok.

Is there a traditional slackbuild script for building this package?

aa.. nop, no Slackpack .SlackBuilds yet :P

Please consider providing one. :) As I'm sure you know, Slackware packages tend to be placed higher on the "trusted" list in the community when packages include a build script.

I'm unable to launch the gui as root...wondering what I might have done to mess it up.
It will launch from the menu with the warning that I'm not root and let me browse files, but when I try to launch from a terminal as root it gives an error that it can't launch the window. Maybe that's a dumb question, but I haven't been able to find much for info on how to fix this. Any help?

Are you logged in as root or a normal user with "su -" in the terminal?

If you are just a normal user, just open a terminal and try (not sure if that should be an upper case S or not)

I get this -

bash-3.1$ ssh -Y root@<localhost> slackpack
The authenticity of host '<localhost> (127.0.0.1)' can't be established.
RSA key fingerprint is <RSA key fingerprint>.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added '<localhost>' (RSA) to the list of known hosts.
root@<localhost's> password:
Permission denied, please try again.
root@<localhost's> password:

{I entered <control> <c> at this point}
This makes me a bit nervous here - May I ask where this info is going, and to what am I connecting?
My understanding is a bit limited here...

Well you probably are not allowing root logins via /etc/ssh/sshd_config. (PermitRootLogin)

Which is not a bad thing if your machine is directly connected to the Internet.

What that command does is simply log into your own machine via ssh but with Trusted X11Forwarding.. allowing you to run the graphical application as root.

Basically you can't log in as one user, su - to another user and run graphical applications without giving that user permission to access your current X session.

You can either use the "DISPLAY/xhost" route or use ssh (which I find much simpler). There are many topics and howto's explaining this.

If you have kde installed you can try which should prompt you for the root password and open the app.

Thank you Mr. Goblin. Yes that does make sense - I was a bit concerned about security issues, there's a lot about that I don't know yet. I will try those suggestions when I next have an opportunity.

* The "kdesu slackpack" did exactly what I was looking for, thank you much for the info on that!
I had a vague idea of the restrictions on a single user per X-session, but your explanation helped a bunch. I can't say I really had that much idea what I was running into (with that) before now, so I now have some reading to do. Once again, thanx...
I've got some system breaking to do :-)

Couple Important Issues
 

Greetz
Before I get to my own stuff allow me to make an important point that applies to several posts in this thread and others regarding running graphic applications as root when logged in to KDE as user. It is my understanding that anything other than KDESU is asking for trouble. You can break KDE using "sudo" or "su" (even with loclahost set). KDESU loads specific libraries and $PATH recognition required by KDE. One must use it for graphic apps and that certainly includes Slackpack. Obviously "su" is fine in CLI, even ncurses apps.

For transition let me say to those who like me miss the "full path to all installed files specific to a package" on old v3 KPackage, that even in Slackware-Current from December 10, 2010 the KDE3-Compat package in Extra will allow you to run the old KPackage, albeit without theme or window decorations. I just renamed the executable to KPackage3 so there would be no confusion.

Now the meat re: Slackpack usage. I love the concept and the layout as well as the overall functionality. For me it is a great successor to "Checkinstall" upon which I have depended for many years, since all I really want to use it for is building and installing packages from source. I don't give a h00t about repositories. I may be just missing something obvious but I can't seem to control "configure" through Slackpack, even if I run both "./configure" and "make" first. If I want to pass any extra options at all like "./configure --enable-amd64" or even "PREFIX=/usr" I can't seem to get Slackpack to follow. It very often creates a package that installs all files to "/" instead of to "/usr" even creating new directories like "/include" which afaik is useless.

Please tell me what I am missing. I have not been able to find much in the way of real documentation.

Thank You

Greetings enorbet (as I can understand from your email we've already mailed eachother :)

Anyway I should inform fellow Slackware users here that I'am working on a way to pass PREFIX options on Create Package command and track installed packages just like the CheckInstall does.