LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-27-2013, 10:34 PM   #241
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 609

Rep: Reputation: 218Reputation: 218Reputation: 218

Quote:
Originally Posted by fl0 View Post
the commerical products don't care , we speak about free software
Any version of it that you deploy for money you have to pay licensing for.

For example, if you sold a cataloging solution to a library system and used the MySQL included with Slackware as the back-end, you'd owe Oracle for that, and you'd have to pass that cost on to your customer. (Or break the law.)

MariaDB will even use your existing my.cnf file and the databases you already have on-disk; it accepts connections and queries from MySQL clients and replicates to or from MySQL servers with no effort other than swapping out the packages. When they say "drop-in replacement," they really mean it.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 02-27-2013, 11:42 PM   #242
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,381
Blog Entries: 15

Rep: Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926
If MariaDB can equally perform as a replacement for MySQL or surpass it, then it should be looked into with care and consideration. However, it must not have any shortfalls in any area.

Remember replacing software with another has to be carefully done. If one package can not perform a critical function that another can, then replacing it isn't an option.
 
Old 02-28-2013, 01:35 PM   #243
+Alan Hicks+
Member
 
Registered: Feb 2005
Distribution: Slackware
Posts: 72

Rep: Reputation: 54
Quote:
Originally Posted by GazL View Post
Just to be clear, I wasn't suggesting that KDE not be part of Slackware, I was thinking more along the lines of having a slackware-kde/ (effectively, the kde,kdei and dependencies from the l set) that goes on top of slackware-xx.x/ but has it's own development schedule.
KDE isn't something that should be separated out. It's far more than just a Desktop Environment, its the basis for hundreds if not thousands of other applications. I have no way to determine the number of "packages" at slackbuilds.org that depend on KDE, but I suspect it to be a non-trivial number. Once you decouple KDE and Slackware, all those packages can now no longer be garaunteed to work. One user may have version X of KDE and another version Y. Even if the script handles both of those well, when KDE version Z comes out the script might have to be largely rewritten again, or an entirely new version of the package you're building may be required, and that version may not work with KDE X or Y.

Granted, this usually isn't a huge problem, but KDE itself is a pretty huge thing and libraries are always subject to change. Additionally, what happens when KDE 5 is released one day? If it's anything like the jump from 3 to 4, you'd see SBo maintainers putting things like "Only works on KDE version 4" in the READMEs of the latest Slackware release.

I don't think you realize just how much trouble such a course of action would be for so little gain.
 
3 members found this post helpful.
Old 02-28-2013, 02:41 PM   #244
GazL
Senior Member
 
Registered: May 2008
Posts: 3,425

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
You raise valid points Alan. The implications for slackbuilds.org hadn't occurred to me.
 
Old 02-28-2013, 08:31 PM   #245
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,381
Blog Entries: 15

Rep: Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926
The KDE desktop and it's applications technically could be excluded while leaving the KDE libraries and header SDK packages alone. GNOME technically is not a part of Slackware any more, but a small assortment of developer packages and runtimes have been added back in for functionality purposes such as support libraries for Xfce. The same could be done for KDE, but due to the fact Patrick uses KDE himself means it's staying for the time being.
 
Old 02-28-2013, 08:42 PM   #246
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 874

Rep: Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809
Quote:
Originally Posted by ReaperX7 View Post
The KDE desktop and it's applications technically could be excluded while leaving the KDE libraries and header SDK packages alone.
Forgive me if I think that idea doesn't make sense. There aren't many (if any) libraries included in Slackware that aren't actually used by something in it.

Quote:
GNOME technically is not a part of Slackware any more, but a small assortment of developer packages and runtimes have been added back in for functionality purposes such as support libraries for Xfce. The same could be done for KDE, but due to the fact Patrick uses KDE himself means it's staying for the time being.
Actually, I've been using Xfce here since the middle of last year. But yes, it is staying.
 
Old 02-28-2013, 10:12 PM   #247
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 806

Rep: Reputation: 362Reputation: 362Reputation: 362Reputation: 362
Quote:
Originally Posted by +Alan Hicks+ View Post
KDE isn't something that should be separated out. It's far more than just a Desktop Environment, its the basis for hundreds if not thousands of other applications. I have no way to determine the number of "packages" at slackbuilds.org that depend on KDE, but I suspect it to be a non-trivial number.
While some popular FOSS applications (like VLC) depend on Qt alone, I don't see hundreds or thousands of other applications depending on KDE. The reason is trivial (and led to the creation of GNOME in the first place): Qt licensing issues. These have been sorted out far to late in 2010. I have hundreds of SBo packages installed on my machines and not a single one depends on KDE. However some of them demand GNOME libs which are not part of Slackware.

I'm not against KDE (it started in Europe after all), but it's not very successful in becoming a stable foundation for third parties. It's mainly a moving target, look what happened to KDE 3.5...

Personally I stick with Xfce, and I'm glad it's now a tier one desktop in Slackware.
 
Old 02-28-2013, 10:48 PM   #248
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 874

Rep: Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809Reputation: 1809
Quote:
Originally Posted by jtsn View Post
While some popular FOSS applications (like VLC) depend on Qt alone, I don't see hundreds or thousands of other applications depending on KDE. The reason is trivial (and led to the creation of GNOME in the first place): Qt licensing issues. These have been sorted out far to late in 2010. I have hundreds of SBo packages installed on my machines and not a single one depends on KDE. However some of them demand GNOME libs which are not part of Slackware.
Um, what? Sure, Qt didn't become LGPL until relatively recently, but before that it was under the GPL for any applications that would also be distributed under the GPL.

If that was a licensing problem, then GNOME still has it.
 
Old 03-01-2013, 08:25 AM   #249
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 806

Rep: Reputation: 362Reputation: 362Reputation: 362Reputation: 362
Quote:
Originally Posted by volkerdi View Post
Um, what? Sure, Qt didn't become LGPL until relatively recently, but before that it was under the GPL for any applications that would also be distributed under the GPL.
Most application developers like to freely choose a license for their own code. Before GPL was QPL and before that FreeQt with even more ridiculous terms. You were only allowed to use Qt/X11, so no multi-platform developments without an expensive commercial license. As said, this was corrected two years ago, but too late for KDE.

Quote:
If that was a licensing problem, then GNOME still has it.
All relevant GNOME libraries are LGPL since the beginning, all ports for all platforms. Even Steam uses some of them.
 
Old 03-06-2013, 05:38 PM   #250
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 1,768

Rep: Reputation: 204Reputation: 204Reputation: 204
Back on topic:

How about adding Alien Bob's multilib package set to slackware64?

Maybe under /extra on the DVD... Or perhaps as an option during installation.
 
1 members found this post helpful.
Old 03-06-2013, 06:02 PM   #251
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.1 64-bit with multilib
Posts: 2,075

Rep: Reputation: 210Reputation: 210Reputation: 210
Quote:
Originally Posted by rkelsen View Post
Back on topic:

How about adding Alien Bob's multilib package set to slackware64?

Maybe under /extra on the DVD... Or perhaps as an option during installation.
I think thats a good idea.


I also still wish to see Blender3D included
 
1 members found this post helpful.
Old 03-06-2013, 09:24 PM   #252
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,381
Blog Entries: 15

Rep: Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926Reputation: 926
Adding in full multilib might not be a bad idea. It would relent some issues with people trying to get 32-bit software working, but there-in lies a problem. It means double packages added in for many existing libraries and programs possibly, which in turn will increase Slackware's overall size, yet again.

The idea should be to slim-down Slackware and put it on a diet, not feed the beast and fatten it up.
 
1 members found this post helpful.
Old 03-07-2013, 02:55 AM   #253
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 806

Rep: Reputation: 362Reputation: 362Reputation: 362Reputation: 362
It would suffice to add i486 libraries to the existing x86-64 Slackware packages. This would add another GB or so to a Slackware64 full install and make it fully compatible with i486 packages. The binaries in bin/32 aren't much of an issue (less than 100 MB).
 
Old 03-07-2013, 03:04 AM   #254
phenixia2003
Member
 
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 293

Rep: Reputation: 166Reputation: 166
Hello

Quote:
Originally Posted by rkelsen View Post
Back on topic:

How about adding Alien Bob's multilib package set to slackware64?

Maybe under /extra on the DVD... Or perhaps as an option during installation.
Users who want to build their own Slackware64+multilib ISO can use mk-slack64-multilib (latest download link). You will find more about this in this thread.

Cheers.

--
SeB
 
Old 03-07-2013, 10:58 AM   #255
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 609

Rep: Reputation: 218Reputation: 218Reputation: 218
Quote:
Originally Posted by rkelsen View Post
Back on topic:

How about adding Alien Bob's multilib package set to slackware64?

Maybe under /extra on the DVD... Or perhaps as an option during installation.
Leaving out multilib is a design decision that Pat made willfully; Pure 64-bit and multilib ready.

I think Eric's compatibility packages are fine just the way they are. One thing that really irritates me about some other distributions that I use at work is that they are always multilib, and I almost never need them to be.

Maybe it's just that I come from a simpler time when hard drives were not measured in terrabytes, but it seems like a waste to me.

I guess that if Pat wanted to do it, having them in /extra wouldn't hurt anything, but as long as an ace like Eric is around to take care of it, I'd rather have Pat spending his time doing other things than wrestling with multilib.
 
3 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
slackbuild textlive on slackware 13 missing texmf tree balamkej Slackware 4 01-21-2010 03:19 PM
A script that could mirror slackware tree from multiple servers grissiom Slackware 8 11-21-2009 07:05 PM
suggestions on family tree programs and..... Chris106 Linux - General 2 10-22-2008 07:54 AM
Linux Family Tree -- Where Slackware Fits unixfool Slackware 16 04-23-2008 11:47 PM
Slackware 9.1 tree/slapt-get question 187807 Slackware 3 02-20-2004 06:36 PM


All times are GMT -5. The time now is 04:38 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration