7 messages in org.freebsd.freebsd-questionsRe: ports question| From | Sent On | Attachments |
|---|---|---|
| Chip | Oct 28, 2000 6:25 pm | |
| Mike Meyer | Oct 29, 2000 11:00 am | |
| Crist J . Clark | Oct 29, 2000 12:07 pm | |
| Chip | Oct 29, 2000 12:39 pm | |
| Mike Meyer | Oct 29, 2000 11:40 pm | |
| Crist J . Clark | Oct 30, 2000 12:11 am | |
| Mike Meyer | Oct 30, 2000 12:31 am |
| Subject: | Re: ports question | |
|---|---|---|
| From: | Mike Meyer (mw...@mired.org) | |
| Date: | Oct 29, 2000 11:00:34 am | |
| List: | org.freebsd.freebsd-questions | |
Chip writes:
Correct me if I'm wrong, but I thought that when installing a port it would also update any dependencies. For example, I want to install xfce from the port, but it failed apparently on esound. So I then went to install esound by itself by it failed with the message that libtool is out of date. So I used pkg_delete on the old libtool and then installed the new libtool port, and now xfce installs just fine because esound also installs fine. I thought stuff like this got updated by installing from the port? This is the first time this sort of problem has happened to me, and I have installed many of the ports just to see what some of these programs are.
Well, "updating" a port isn't something the ports system deals with every well. It tries to *install* the dependencies if it can't find them. Libtool seems to break under these conditions, but it's the only thing I've run into that does. Other ports have simply installed multiple versions of the port.
<mike
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message