Re: A rosetta stone of package names?

[Tim Post]

Hi Ralf,

On Sat, 2008-07-26 at 12:46 +0200, Ralf Wildenhues wrote:
> How would that work?  On this system I'm sitting at, you'd have to be
> super user to install, and while I may be in charge, I'm certainly not
> going to hand out the password to your configure script; neither will I
> compile sources as super user.  On another system, the only way to
> globally install software is to write a friendly mail to the people in
> charge.  On the next again, it is not even possible to locally (i.e.,
> below $HOME) install additional software compiled from source.

If the user installed and compiled the library within the confines of
their home directory, it would work.

Albeit, /home/homer/libfoo/ does not exist on any system but that one :)

The point is the user can compile and use the program under most
circumstances.

> No, but I do know that going the other way round, i.e., from distro
> packaging tools like rpm or apt, to building sources already works very
> nicely.  For example "apt-get source ..." or "apt-get build-dep ...".

That's what I'm trying to translate. libfoo-dev or libfoo-devel, or
libfoo9-dev or -devel? If I am not root, what is the URL to get the
sourceball in order to use the library without bugging root to install
it?

Such a look up table would be priceless, I think :) I have had zero luck
in finding one.

Cheers!
--Tim