Quote: Original post by George2
...
Btw, This GPL bashing is getting annoying (don't like the license, don't use the code licensed under it, is my advice)

I couldn't agreem more. If it weren't GPL'd people wouldn't even see the code, even far use it, and now they complain about that?

I don't use many GPL libs while coding, but if any of you people wanna see my sourcecode, just ask for it. What's the real value in free software anyway? Knowledge? Just spread and be happy about that you just helped somebody do something useful... that's my 2 cents anyway. Sure . I'm not into software development for work.. and back in the days when I were, we coded everything ourselfs instead.

Sorry for spinning away from the dependency topic

Albert

"I couldn't agreem more. If it weren't GPL'd people wouldn't even see the code, even far use it, and now they complain about that?"

I don't know about that. Linux has become more popular, but it's hard to say if that's the reason. I don't have anything against open source. I just don't like strings attached. If you don't like "whatever you like" bashing you shouldn't read forums at all. I can't stand people that try to control discussions with BS either. There are advantages to dynamic linking, it's just a pain. I don't think apt-get or the many other package managers really solve it. They just cover the complexity with wizard like structure. That's kind of a Microsoft solution to things.

Quote: Original post by fireside
If you don't like "whatever you like" bashing you shouldn't read forums at all..

You've got a point there

Hello All,

I have to say fireside has a very good point.

It is find to link in dynamic libs. But there need to be some thought about this also.
Developers should try to reduce as much as possible the external links a program has.
It can be a nightmare to figure which out of 30 libraries a problem could be in.
Also if libraries are written poorly they can include links to other libs.
If you use a library and it is not a widely installed library and you only using a few method look to see if you can do with out them.

Another Thing I don't like is you have to have like 20 different sets of build tools compile and install in right area and of the right version for the configure / makefiles to work.

That is bigger problem.

Lord Bart :)

Anybody who feels sadomasochistic should try to compile vlc media player

dependency hell one click away

Quote: Anybody who feels sadomasochistic should try to compile vlc media player

That's nothing. Try compiling Gnome by hand.

I use the distro I use (Source Mage) for exactly this reason. Being a source-based distribution, the distinction between packaged software and software installed by hand is minimal.

But even when I was still using Mandrake, dependency hell was not a problem (back when I used Redhats 5 and 7, though, it was definately a huge problem). I would just use RpmDrake, or whatever it was called, which took care of the dependencies in the same way it took care of the software that depended on them.

Dependencies?

I haven't had that problem since I stopped using Red Hat 5 back in the days.

Debian, Welcome to the Real World BABY!!

Quote: Original post by wizards
Dependencies?

I haven't had that problem since I stopped using Red Hat 5 back in the days.

Debian, Welcome to the Real World BABY!!

This must be seconded. And Ubuntu and otehr debian-derived distros, too.

There are no dependancy problems on debian.

# apt-get install vlcReading Package Lists... DoneBuilding Dependency Tree... DoneThe following extra packages will be installed:  libdvbpsi3 libtar libxosd2 ttf-freefont wxvlcSuggested packages:  xfonts-base-transcoded vlc-plugin-alsa mozilla-plugin-vlcRecommended packages:  x-ttcidfont-conf ttf-thryomanes videolan-docThe following NEW packages will be installed:  libdvbpsi3 libtar libxosd2 ttf-freefont vlc wxvlc0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.Need to get 6458kB of archives.After unpacking 15.6MB of additional disk space will be used.Do you want to continue? [Y/n]

and while apt-get gnome works, too (the other suggested problem with dependancies), gnome can be built with amazing ease with jhbuild (or so I hear, I'm not insane enough to build anything by hand)

Quote: Original post by Kylotan
I was amazed that I was expected to download 136MB of kernel source just to compile a driver.

So... you'd like it to be more modular?

Quote: I have lots and lots of libraries that I had to install for individual programs that required them.

So... you'd like it to be less modular?

Quote: I'd like to be able to see at a glance what libraries something requires, and how big those libraries are (or at least were when this package was built).

Debian, aptitude. [grin]

Quote: Original post by Anon Mike

Quote: There are lots of distros and package management systems out there--pick one and move on.

This is actually part of the problem. There are 10 billion options out there, all of which range from completely different to subtly incompatible.

This is both a disadvantage and an advantage. Since there are so many options you can almost always find the right one for you. The problem is that the right one for you is always going to be anywhere from slightly to enormously different to what is the right one for any other person.

Quote: Original post by Doc
This is both a disadvantage and an advantage. Since there are so many options you can almost always find the right one for you. The problem is that the right one for you is always going to be anywhere from slightly to enormously different to what is the right one for any other person.

Yeah, but they slowly come around to an actual solution.

For example, let's take a look at the major players in distro land today.

Novell, Red hat, and debian[-based] distros.

These three are the big ones. Take note, for example, that all three either tend to, or outright embrace Gnome as the desktop of choice. All three attempt to support that whole LSB thing (marginal though it may be for now).

Not to say that there aren't disagreements. Java vs C# vs "OMG Java is nonfree and mono won't build on s/390!" (Debian does deserve a few good digs, but at least repos with java and mono in them are a very short sources.list addition away...) But on a lot of the core issues, things are getting more unified than it might seem.