From owner-freebsd-ports Tue Jan 2 21:18:34 2001 From owner-freebsd-ports@FreeBSD.ORG Tue Jan 2 21:18:31 2001 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from indigo.external.org (c1118643-b.chmpgn1.il.home.com [24.181.130.163]) by hub.freebsd.org (Postfix) with ESMTP id 1B26337B400 for ; Tue, 2 Jan 2001 21:18:31 -0800 (PST) Received: (from jeremy@localhost) by indigo.external.org (8.11.1/8.11.1) id f035G5986848; Tue, 2 Jan 2001 23:16:05 -0600 (CST) (envelope-from jeremy) Date: Tue, 2 Jan 2001 23:16:05 -0600 From: Jeremy Shaffner To: Richard Browne Cc: ports@freebsd.org Subject: Re: Ports, shared libraries, dependencies and versions Message-ID: <20010102231605.B84037@external.org> References: <002501c0752a$ef9b1c10$0e1a24cb@scorpio> <20010102214719.A84037@external.org> <000701c0753c$fd782190$0e1a24cb@scorpio> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000701c0753c$fd782190$0e1a24cb@scorpio>; from richb@pobox.com.au on Wed, Jan 03, 2001 at 03:23:57PM +1100 Sender: jeremy@indigo.external.org Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jan 03, 2001 at 03:23:57PM +1100, Richard Browne wrote: > > > releases, for example, will be binary compatible. Wouldn't it make sense > > > then for FreeBSD ports to depend on 'gtk-1.2.*'? > > > > Don't confuse the naming convention used for ports & packages with the > naming > > convention used for shared libraries. You *could* upgrade to 'gtk-1.2.9' > > because the actual dependancy is on "gtk12.2". You would simply: > > > > # cd /usr/ports/x11-toolkit/gtk12 > > # make clean (if you didn't clean from last time) > > # make > > # pkg_delete gtk-1.2.8 (this way you've made sure the new version compiles > first) > > # make install > > > > Ok, I see. Packages don't depend on 'gtk-1.2.8'. But hang on, that's what > the ports system says (see http://www.freebsd.org/ports/gnome.html for gtk-1.2.8 just happens to be the current version of the Port. > example). How can I find out what the actual dependencies are then? You can peek at the Makefile for a particular Port. It's the *_DEPENDS macros that define what the Port depends on. This is how the ports system handles automatically installing dependancies. > > Your pkg_delete will complain (you may have to force it), but you can > ignore > > the warnings. > > If I have to force it and ignore warnings.. isn't that a blow to user > friendliness? Granted, the main thing is that it can hold together and > handle updates, but it's not clear to a new user. How do I know if it's > valid to use pkg_delete and ignore warnings? A new user isn't likely to be waiting for the latest minor upgrade to some random graphics toolkit. They're more likely to notice when GNOME itself has a new release, and they can install it (and all it's newer dependancies) the same way the did the first time. You could also skip the pkg_delete. You'd have two registered versions of GTK (though only one actually installed). Everything would work but you'd have a cluttered /var/db/pkg/. -- --------------------------------------------------------------------- Jeremy Shaffner | This space for rent. jeremy@external.org | $ grep happiness life http://www.external.org/~jeremy/pgp.key | FreeBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message