Re: FatELF patches...

From: Ryan C. Gordon
Date: Mon Nov 02 2009 - 13:18:51 EST



> With my Debian Developer hat on...

I'm repeating myself now, so I'm sorry if this is getting tedious for
anyone. FatELF isn't meant to replace the package managers.

tl;dr: If all you have is an apt-get hammer, everything looks like a .deb nail.

> That usually ships as sources or prebuilt binaries in a tarball - target
> /opt and voila! For a bigger audience you'll see a lot of experimental
> stuff that gets packaged (even in quick'n'dirty mode).

"A lot" is hard to quantify. We can certainly see thousands of forum posts
for help with software that hadn't been packaged yet.

> > software that isn't appropriate for an apt/yum repository
>
> Just create a repository for the damn thing if you want to distribute it
> that way. There's no "appropriate / not appropriate" that applies here.

I can't imagine most people are interested in building repositories and
telling their users how to add it to their package manager, period, but
even less so when you have to build different repositories for different
sets of users, and not know what to build for whatever is the next popular
distribution. For things like Gentoo, which for years didn't have a way to
extend portage, what was the solution?

(har har, don't run Gentoo is the solution, let's get the joke out of our
systems here.)

> > software that distros refuse to package but is still perfectly useful
>
> Look at what happens today. A lot of that gets packaged by third
> parties, and more often than not they involve distribution
> maintainers. (See debian-multimedia, PLF for Mandriva, ...)

I'm hearing a lot of "a lot" ... what actually happens today is that you
depend on the kindness of strangers to package your software or you make a
bunch of incompatible packages for different distributions.

> > closed-source software
>
> Why do we even care?

Maybe you don't care, but that doesn't mean no one cares.

I am on Team Stallman. I'll take a crappy free software solution over a
high quality closed-source one, and strive to improve the free software
one until it is indisputably better. Most of my free time goes towards
this very endeavor.

But still, let's not be jerks about it.

> Tarball,

Ugh.

> /opt,

Ugh.

> static build.

Ugh!

I think we can do better than that when we're outside of the package
managers, but it's a rant for another time.

> And, about the /lib, /lib32, /lib64 situation Debian and Debian-derived
> systems, the solution to that is multiarch and it's being worked
> on. It's a lot better and cleaner than the fat binary kludge.

Having read the multiarch wiki briefly, I'm pleased to see other people
find the current system "unwieldy," but it seems like FatELF "kludge"
solves several of the points in the "unresolved issues" section.

YMMV, I guess.

--ryan.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/