SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well, I gave it a shot at creating a package. I pointed it to dvdauthor as a test package, and it created the package in root's home. While it did work this time, its not something that gives me any control over where it goes or any extra parameters I may wish to add.
That said, overall it can be a useful app, and I think congratulations are in order for your work on this project.
after qmake && make the slackpack executable is created at the 'bin' folder.
it does not installs itself into the system, however, you can just copy "Slackpack" executable from the /bin directory of the source into '/usr/bin', and run it from everywhere
* 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)
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
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 =]
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.