apt-get under slack

[sheek]

When i run the apt get install command
it says that it cannot find /var/lib/dpkg/lock file
and asks if i am root
(yes i was)

are there any other things to configure besides my sources list for apt ?

[Strike]

Um, why are you using Slack if you want to use APT ?

[evilcartman]

yeah slack doesnt have apt-get does it?

[2thumbs]

Hmmm I don't know if there is a apt-get thing available for slack... I know it works fine in mandrake :D

[ 28 January 2002: Message edited by: 2thumbs ]

[PimpHolic]

apt in slack~!!!!!!!!!!!!!!!!!

HOW HOW HOW!!
MAKE AN NHF!!!

[Syngin]

Originally posted by Strike:
<STRONG>Um, why are you using Slack if you want to use APT ?</STRONG>

I was a little surprised too. Is apt-get compatible with Slack?

[sheek]

yeah apt was ported to slack
so now you can have the best of both worlds if you can configure the fscking thing http://project-csi.sourceforge.net/apt-get.tgz &lt;- the file http://project-csi.sourceforge.net/ &lt;- top level

if these links don't work then check linuxpackages.net
Don't shoot me i'm just the messenger
does anyone have the answer to my question btw ?

[ 28 January 2002: Message edited by: sheek ]

[knute]

Ok, this is just a total guess here, but I looked at my own /var/lib/dpkg file (I run Debian), and found 2 files, one was lock and the other methlock. Both files were 0 length.

So basically as root you could try:
touch /var/lib/dpkg/lock
chmod 640 /var/lib/dpkg/lock

Then retry it.
The only reason that I mentioned the other one was because it was there, but I'm not sure if it is important or not. 8o)

[Strike]

No, the question remains - why would you use Slack if you are going to use APT? APT enforces upon your system a filesystem hierarchy that the packages follow, including an init structure (unless this "port" is really more of a "conversion" and changes things like that). Change Slack's filesystem and its init structure and add APT to it, and you basically have Debian anyway. So, if you really want to use APT, just use Debian - the system it is DESIGNED to work on.

[X_console]

I'd have to agree with Strike. If you want to use apt, use Debian because it was made for it. If you use apt for Slack you're sure to run into problems eventually. This is the same reason as why I don't run rpm on Slack.

[evilcartman]

its like rpm+deb+tgz ;-)

[Ludootje]

use kpackage, it's a kde tool with which you can install debs&rpms on any distro you want.

[Strike]

Originally posted by Ludootje:
<STRONG>use kpackage, it's a kde tool with which you can install debs&rpms on any distro you want.</STRONG>
Yes, but this is bad for many reasons:
Using RPMs and debs together on a system means you have two conflicting package databases which cannot talk to one another (unless kpackage uses some kludgery to get them to which is still kludgery at best)
You would have to maintain two databases which are kinda sizable (though not really in the grand scheme of things)
RPMs and debs follow different filesystem layouts (similar, but still different)

And a number of other reasons but mainly the first one.

[Ludootje]

Originally posted by Strike:
<STRONG>Yes, but this is bad for many reasons:
Using RPMs and debs together on a system means you have two conflicting package databases which cannot talk to one another (unless kpackage uses some kludgery to get them to which is still kludgery at best)
You would have to maintain two databases which are kinda sizable (though not really in the grand scheme of things)
RPMs and debs follow different filesystem layouts (similar, but still different)
And a number of other reasons but mainly the first one.</STRONG>
I don't say it's good, but at least it works, I think using RPMs/DEBs on a system which isn't made for it is by default bad for your system.

[viscia]

I can think of a reason to do this. You've got your home on ReiserFS. Ignoring that I suspect many of us Slackers just like doing things the hard way.

[ 29 January 2002: Message edited by: viscia ]

[Strike]

Originally posted by viscia:
<STRONG>I can think of a reason to do this. You've got your home on ReiserFS. Ignoring that I suspect many of us Slackers just like doing things the hard way.

[ 29 January 2002: Message edited by: viscia ]</STRONG>
How is this a justification for trying to use apt on a system it is not designed for?

[Strike]

Okay, since I'm getting flack about this on IRC I thought I'd post my reasoning a bit more in depth on here so perhaps people will realize the point I'm trying to make is quite valid.

As I understand it, using apt on another system still relies on using existing apt mirrors and existing packages (except the RPM port of APT made by Conectiva). If this is not the case (which I'm assuming is not since no one has rebutted my argument about the set filesystem hierarchy/init style), then of course apt will work marvelously assuming the new packages are set up in an intelligent manner.

However, using existing packages designed to work on a Debian system will essentially transform your system into a Debian system if you use the package system correctly. Part of the main goal of a package system is to contain an accurate record of what is installed on your system. This means that everything on your system should be installed via that package system in order for it to fully achieve this goal. This includes the package system itself and the init scripts for the system. Strip these two things and the package system away from a distribution and you have nothing that resembles that distribution aside from MAYBE config tools that DEPEND on some of the stuff that you have just obliterated anyway.

[kuber]

I am with Strike on this.
Just use debian if you must have apt-get.
Personally I like using slack and installing everything but the base system from source and using install-log (check freshmeat) to manage files.