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.
Hi every slacks,
I am new to slack, while i used for longtime redhat and debian. I want to know if there is in slack, something like apt-get ( I mean dependances solved software).
For 3rd party packages for Slackware have a look at: http://slackbuilds.org/
Although it does not resolve dependencies like APT, the program sbopkg will somewhat automate the process of compiling slack-build packages: http://www.sbopkg.org/
Slackware's package format does not support dependency information, so any program that tries automatic dependency resolving is a hack - it may work, and it may just as well not work.
Some 3rd party packages contain additional "meta information" regarding additional packages it depends on, but you can never be certain what packages do and what packages don't contain this information.
The best dependency resolver in Slackware is the user himself - do not rely on 3rd party programs that try to do this for you. This is part of the Slackware philosophy, and will not change in future.
The best dependency resolver in Slackware is the user himself - do not rely on 3rd party programs that try to do this for you. This is part of the Slackware philosophy, and will not change in future.
Eric
The KISS philosophy of Slackware is one of the many reasons I'm a Slacker.
I don't need a package manager.
One of the things that scared the heck out of me when I first started with Slackware was the dependency "issue" as my only experience was with Debian based distros. I gradually learned that it was NOT an issue at all....which is the beauty and simplicity of Slack. Virtually anything you could ever want or need is either already included or available from SlackBuilds, Slacky.it,Linuxpackages, AlienBob and others. Any and all requirements are usually clearly indicated and hardly a concern.
Give it time...all of a sudden things will just "click" for you and you'll find it hard to go to another distro...and I'm just using Slackware for about 6 months!
already included or available from SlackBuilds, Slacky.it,Linuxpackages, AlienBob and others.
If you remove Slacky.it and Linuxpackages you have it right. rlworkman.net is another as well. Stick to anything that is a .SlackBuild and you will be fine.
The KISS philosophy of Slackware is one of the many reasons I'm a Slacker.
I don't need a package manager.
I don't agree at all!!!
Firstly ... Try to install manually lyx for example, which depends on texlive ( a huge software) and tell me.
Secondly .... to allow maximum of people tu use linux (any distro ), we have to deliver it as easy as possible, numbers of public users is more important than "specialists".
One of the reasons I left redhat (fedora, I started with redhat 4.0 ten years ago) and adopt debian is apt-get.
Now why not slack, I am testing vectorLinux, if adding and removing package is not a hard task.
Whilst you may not agree, every dedicated Slacker, knows and understands why the Slackware way is best.
I like you started many years ago, redhat 5.2 for me, and I progressed through Debian. However until you lose all your data because someone has said you must upgrade glibc and this breaks your system, and apt-get etc cannot downgrade your system even with a force, then you will not understand that it is better to have fine grained control over what goes on your system.
Slackware may make you work a bit harder, but it upgrades your knowledge and increases your data safety. No data lost since I started using Slackware March 2004.
Slackware's package format does not support dependency information, so any program that tries automatic dependency resolving is a hack - it may work, and it may just as well not work.
Thinking about dependency checking, I think it could be possible to store dependency information outside of packages - on external server, perhaps, or as separate package.
Quote:
Originally Posted by abd_bela
Firstly ... Try to install manually lyx for example, which depends on texlive ( a huge software) and tell me.
Since when just one dependency is a problem even if software is huge? I could understand if you mentioned GnuCash, banshee or something that have few dozens packages that needs to be built in certain order.
Quote:
Originally Posted by abd_bela
to allow maximum of people tu use linux (any distro ), we have to deliver it as easy as possible
Nobody "has" to do anything. And "we" don't have to deliver it as easy as possible or allow maximum number of people to use linux/slackware - since it won't help distribution in any way. If you disagree, remember those annoying "Jehova Witnesses" who try to deliever their religion to maximum umber of people.
Distribution shouldn't attempt to be "easy for everyone" - because there always will be at least one person that "won't get it". And distribution shouldn't attempt to convert all people to linux/slackware - people should decide themselves what to use.
Secondly .... to allow maximum of people tu use linux (any distro ), we have to deliver it as easy as possible, numbers of public users is more important than "specialists".
We do.
Quote:
One of the reasons I left redhat (fedora, I started with redhat 4.0 ten years ago) and adopt debian is apt-get.
Now why not slack, I am testing vectorLinux, if adding and removing package is not a hard task.
best regards
bela
Best of luck to you with that then.
If you decide to come back, our community is TOP NOTCH. You'll never find a more 'willing to help' crowd or will you find so many willing to help you.
If you remove Slacky.it and Linuxpackages you have it right. rlworkman.net is another as well. Stick to anything that is a .SlackBuild and you will be fine.
agentcOre,
So I take it just using installpkg on a .tgz can still be inviting trouble? I'm still in a serious learning curve with Slackware...so all
sage guidance is most appreciated.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.