|
|
Subscribe / Log in / New account

Swimming against the tide.

Swimming against the tide.

Posted Aug 6, 2008 19:45 UTC (Wed) by drag (guest, #31333)
In reply to: Swimming against the tide. by sladen
Parent article: Freespire moves back to Debian

> Surely if "it's $X that does most of the work", but "$Y didn't give a crap about
compatibility" then it would make it very hard (impossible?) for $Y to do all that leeching
from $X...


No it's not. 

What you do is this:

Start off with a Operating System that is essentially a snapshot of Debian Unstable. 

Then go and modify and break a bunch of existing functionality in order to add your own.  Say
edit some INIT scripts so that they work well with a newer version of Network-Manager (or some
other new sort of thing) without caring of your changes break a bunch of other scripts that
depended on what your editing. 

Then update a bunch of packages, remove a bunch of packages you don't like, and change things
around so that the versioning numbers are different and files sorted with package X on your
custom distro are conflicting with package Y provided by Debian.. which you don't plan on ever
using so it's not a big deal.

And then on top of that while your doing all of this Debian has started introducing newer
versions of packages that you've modified.

----------------

Look at it this way:

It's a hell of a lot easier and you get your work done much faster if you don't care about
compatibility.

Package compatibility takes a lot of extra effort and testing. It's a hell of a lot easier to
break something and have it work for your specific task then it is to modify it while making
sure that it still works.

----------------


If you don't believe me, find out yourself. 

Take all the Gnome packages built for Ubuntu and then install them on Debian Lenny. Get back
to me on how well that works out for you, although I really doubt anybody has to try that out
to guess how well that would work out.

I believe that Ubuntu re-bases itself off of Debian for each release. So this isn't a serious
problem were distributions have diverged off into 2 entirely different directions. I
understand that a lot of work that Ubuntu does goes back into Debian. It just takes extra
effort.


---------------------------

> "[I]t's about time that the Ubuntu vs Debian thing goes by the wayside"; one would hope so.
There are quite a few Debian developers out there, of which 2% happen to be on the payroll of
a certain Ubuntu backer. It must be so annoying to spend 40 hours per week swimming one way
and the other 40 hours per week swimming in the opposite direction.


What ends up happening is that you end up just doing everything twice. Once for Ubuntu and
again for Debian.

What I am trying to point out here is how nice it would be that people would only have to make
a package one time and have it work in both distros.


to post comments

Swimming against the tide.

Posted Aug 6, 2008 19:57 UTC (Wed) by drag (guest, #31333) [Link]

Oh and I didn't say that Ubuntu was _leaching_ off of Debian.

Far from it. 

Ubuntu using Debian as a base is the best thing they've could of done. Because god knows we
don't need another distro or another person repackaging everything.

If Debian does a good job and Ubuntu can use it they _should_ use it.

Swimming against the tide.

Posted Aug 7, 2008 7:39 UTC (Thu) by dgm (subscriber, #49227) [Link] (2 responses)

That's not different of what Debian themselves do with the software they package.

The packagers pick some version of a program, add and move stuff around so it matches the
distro's policies and put custom fixes on top when problems are found. More often than not,
Debian's fixes are not pushed back to the original code, that has probably moved on. 

That's life. Building a derivative only saves you so much work. 

AFAIK, only Slackware is free from this, because they the software as is.

Swimming against the tide.

Posted Aug 7, 2008 12:45 UTC (Thu) by pjdc (guest, #6906) [Link]

More often than not, Debian's fixes are not pushed back to the original code, that has probably moved on.
Are you sure about this? Debian developers are encouraged to feed changes upstream, and thanks to apt-listchanges I get to see plenty of remarks in changelogs about Debian patches actually being merged upstream. Of course, plenty of others are dropped due to upstream fixes and changes rendering them obsolete.

Swimming against the tide.

Posted Aug 7, 2008 16:14 UTC (Thu) by drag (guest, #31333) [Link]

Well I wasn't trying to make out that Debian is godlike and they do no wrong. I am sure that
they are as guilty at it as anybody.

And the Slackware attitude to dependency tracking with software packages is pretty much
correct. It's a nice feature, but it's not the best way to solve many of the problems faced
with Linux software distribution.


> That's life. Building a derivative only saves you so much work. 

The ideal situation is the upstream developers package the software themselves and then
distributions collect them, test them, and then provide them to their end users.

That should be the ultimate goal for software distribution.. people package their own software
and it 'just works' on all distributions.

All the distributions that get released around the same time all use the same software.
Similar versions of OpenSSL, Xorg, Linux, GCC, etc etc. Having a dozen different people tweak
all these applications in dozen different ways is kinda silly seeing how little it actually
benefits end users. 

I mean, as a end user.. Is the GCC provided by Suse is going to be different enough and
provide compelling improvements compared to the version shipping with CentOS, Fedora, Debian,
Ubuntu, Slackware, etc etc? Is it possible justify the amount of duplicate work that all these
people put into building and packaging their own very-slightly-different versions when there
is so much other important work that these guys could get done by working together?

And if Suse did indeed have some dramatic improvement to their GCC version.. wouldn't it be
nice if Debian users could just copy it off of Suse's FTP server or installation cdroms and
use it? No worries? That the GCC developers could just suck down the patches and use them
without worrying how it may break something in Debian?

I like the idea of high quality binary distribution of open source software. But maybe there
are other ways.. rpm2git seem interesting.

Maybe it can be extended to support debs... I don't know. It could be a useful way to start
smoothing out the trivial differences (that pop up as stumbling blocks for users) between
distributions and lead to higher amounts of software compatibility.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds