SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Its been a while since we lastly posted something. We have been working on the 3.8 release.
This said, now we are ready to release a direct upgrade to the dropline GNOME 3.6 release
for Slackware 14.0 both archs. To not make a short story long I invite you to check more
details about this on our <a href="https://sourceforge.net/apps/trac/dropline-gnome/wiki/DroplineGnome3_8" title="sourceforge.net wiki">sourceforge.net wiki</a> page.
On this page you will be able to find more detailed information on what has changed.
Although we usually do an alpha release quite stable it does not mean is bug free, this means
that we are counting on your help also to get us that non working stuff sorted out
and help create a final stable release.
You can get the installers from the following locations:
Just forgot to clarify what we consider ALPHA state. This means we have built all the packages and we mainly need to fix configuration issues. Normally after alpha state we do not add or remove packages. The desktop is very usable but from time to time we can get some crashes or some non working programs. So if you want to try it it should not make you scared to loose some of your data.
Oh ok, just forgot to mention that we have, thanks to Eugene Wissner, a working PackageKit and gnome-packagekit. For now it only permits us to get the slackware updates as it uses slackpkg as a backend, but shorty we plan to expand it and allow third party repos.
Oh ok, just forgot to mention that we have, thanks to Eugene Wissner, a working PackageKit and gnome-packagekit. For now it only permits us to get the slackware updates as it uses slackpkg as a backend, but shorty we plan to expand it and allow third party repos.
No.. Slackpkg+ is not a really good solution. Slackpkg doesn't give respective return codes on errors (what makes it very difficult to work with its outputs), the format of the package database isn't so suitable since PackageKit gives on request additional information about packages (for example if you search for name or something else, it prints also the short description), moreover some functionalities aren't achievable with Slackpkg. It is actually possible to implement a backend for PackageKit in shell (the most, a small part should be written in C) but it requires that the program supports "PackageKit output format", otherwise you have to parse the output yourself and it is difficult and has an influence on the performance. Actually the parts that aren't relying on Slackpkg (for example search functions search in the Slackpkg files but Slackpkg itself isn't called) work much faster than original Slackpkg.
And Slackpgk+ isn't really a plugin, it is rather a hack around restrictions of Slackpkg, I can't say I like the way how it is written; it would be much more useful "to replace" slackpkg with slackpkg+ (I mean it could be useful to update old and good /usr/sbin/slackpkg too).
I want to say with this text that Slackpkg(+) was developed for other purposes. I thought in the beginning: I take slackpkg, start it and everything is done, but now I don't see it so simply. The only that one can do is using Slackpkg as template, stable and very well proved Slackpkg could be a wonderful template for a nice C (or other language) program.
Yes, because I have used the x86-64 index file to create the i686 , but all those packages, unless I did some error should
be marked as obsolete, and the installer should un-install them also at the end.
About gedit, we will ship gedit and accerciser and some other packages too from the 3.6.x series as they do not require python3.
But its good that you pointed this out as I have completely forgot about that detail, and will fix that stuff as a priority.
It is a bit annoying to have all that stuff listed every time you run the installer, and this is also on my TODO list to be fixed
before BETA is released.
NetworkManager-0.9.8.2-2dl - rebuilt with ModemManager 1.0.0 support
cantarell-fonts-0.0.14-1dl - normal update
accerciser-3.6.2-2dl - rebuilt agains the 3.8.x platform, this one should also uninstall the x86_64 version installed on i686 arch.
Hopefully I can get gedit and gedit-plugins built shortly and update them.
Please after runing the installer to get the updates remember **to install slackwares libarchive** again, because we have tried to upgrade it but it has no sense to use a newer one, so with this set of updates libarchive from dropline is marked as obsolete_lib and installer will uninstall it.
YOU MUST INSTALL THE SLACKWARE LIBARCHIVE AGAIN BY YOURSELF.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I have a question
