pkgtool

**vwgtiturbo** · 01-30-2004, 06:44 PM

What do you know? 12 hours into running Slack, and I already have a little problem. Apache 1.3... Why httpd.conf listed /usr as the serverroot (not document root) I have no idea. I couldn't find squat in /usr concerning apache... Anyways... The last time I ran Slack, I could not get the webserver to work. It started correctly, I configured it, but when I tried to access the page, I was slapped with a forbidden access error. So, what I decided to do was upgrade to Apache 2.0.
I was reading the Slackware documentation from their site, and they said that .tar.gz packages and .tgz packages are the same, but just named differently due to personal preference. So, if I download a .tar.gz file, I should just be able to rename it to .tgz, and the pkgtool will be able to handle it?
I assumed that the above was true, so I downloaded apache2.tar.gz (not the exact name, but the extension was .tar.gz). I ran "upgradepkg apache1.3%apache2" and let it go. All it ended up doing was deleting some files (according to standard out) then said that it was upgraded. I tried to run httpd or apache, no luck. I tried to FIND apache or httpd, no luck. I opened the pkgtool, and it said that httpd2 was installed, but it did not have a description, unlike all of the other packages. It was like the package wasn't there. So, to avoid confusion, and possible litter files all over the system, I removed httpd2 via package tool (who knows if it were even on the system...) and deleted any reference to apache or httpd. I will start over, and install apache 2.

**vwgtiturbo** · 01-30-2004, 06:49 PM

if I remove something with the package tool, will it's respective entries for startup be removed? I need to remove httpd from the startup, as I no longer have it installed. rc.httpd? I am not yet familiar with the whole startup script process... obviously...

**vwgtiturbo** · 01-30-2004, 06:53 PM

okay, here's what happened... when I upgradepkg'd from apache 1.3 to apache2, it simply deleted a few of the 1.3 files (I still had to delete alot of them manually, modules, conf, etc.) but THEN it SAID that it installed apache2, but what it really did was simply untar the .tar.gz file into a httpd2 directory in /. So, am I correct in assuming, by this behavior, that just because a file is in .tar.gz format doesn't necessarily make it Slackware ready? I just figured that with if it were, then upgradepkg would have done more than simply untar the archive...

**gaxprels** · 01-30-2004, 06:57 PM

Ok, to run apache try this:

/usr/sbin/apachectl start

.tgz is just an abbreviation for .tar.gz, BUT that does NOT mean that every .tar.gz / .tgz you can download can be installed by pkgtool. pkgtool handles slackware packages only. You must use pkgtool to remove your old apache, then do a source install "./configure && make && make install" of apache 2 if you want that.

Personally, I'd reinstall the apache that came with slack, and use that instead

**vwgtiturbo** · 01-30-2004, 07:03 PM

Is there any particular reason you would do that? I don't know... It was just really odd, having the same error I did last time, and not being able to find anything online about it. I found some things, but either they didn't apply, or they were greek to me (and I felt that the reason wasn't the problem, only because I have a simple op going here, nothing special)

**gaxprels** · 01-30-2004, 07:08 PM

I'd reinstall the apache that came with because it will be easier to grab it from your CD with pkgtool :P

Seriously, after you reinstall the deleted files, run "/usr/sbin/apachectl start" then tell us what your errors are from there.

**vwgtiturbo** · 01-30-2004, 07:12 PM

One last quesiton before I go to the airport...

How would you delete something installed by makeinstall? Would you simply delete it's installation directory and be done, or is there a log of the files it installed and where it put them, and you just chase all of the files down and get rid of them?

**gaxprels** · 01-30-2004, 07:15 PM

Well... I know there is a way to determine what files went where without looking at the "install" line in each Makefile, but I can't remember how it's done. If you NEED to uninstall something, then you can always resort to looking at the "install" line in the Makefile in the root of the src tree for that program and see what files are copied where

**gaxprels** · 01-30-2004, 07:20 PM

Oh... one more thing... some Makefile's include an "uninstall" section, so running "make uninstall" (or in my case: "sudo make uninstall") should work.... might check for that as well...