Date: Tue, 03 Oct 2000 09:57:55 -0700 From: bmah@FreeBSD.org (Bruce A. Mah) To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: Neil Blakey-Milner <nbm@mithrandr.moria.org>, Akinori -Aki- MUSHA <knu@idaemons.org>, freebsd-ports@FreeBSD.org, bmah@FreeBSD.org Subject: Re: Enhancement of pkg_version's version comparison routine Message-ID: <200010031657.e93Gvtg10718@bmah-freebsd-0.cisco.com> In-Reply-To: <39D9EE01.7A880665@FreeBSD.org> References: <86k8by6eis.wl@archon.local.idaemons.org> <20000927002401.A73341@mithrandr.moria.org> <39D9D006.652DC258@FreeBSD.org> <20001003161027.B67542@mithrandr.moria.org> <39D9EE01.7A880665@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_320064253P Content-Type: text/plain; charset=us-ascii If memory serves me right, Maxim Sobolev wrote: > Neil Blakey-Milner wrote: > > > On Tue 2000-10-03 (15:24), Maxim Sobolev wrote: [Use @option or @comment PLIST variables to track where intalled packages came from, maybe with a fallback to INDEX.] > > Take zsh and zsh-devel, or any of those devel packages - how do you tell > > which one to follow when it moves from zsh-5.0 and zsh-devel-6.0 to > > zsh-7.0 and zsh-devel-8.0? > > > > I like your idea, though. That just seemed to leap at me. > > Hmm, I do not see any problems, for example: > > Moment of time t1: > - you have installed foo-5.0 and foo-6.0 from somecategory/foo and > somecategory/foo-devel ports; > > Moment of time t2>t1: > - the ports have been upgraded, so you now have foo-7.0 and foo-8.0 for foo a > nd > foo-devel ports; > - pkg_version looks into foo-5.0 installed package and determines that it sho > uld check > somecategory/foo to determine whether update necessary. It does so, BAH you h > ave to > upgrage to foo-7.0; > - pkg_version looks into foo-6.0 installed package and determines that it sho > uld check > somecategory/foo-devel to determine whether update necessary. It does so, BAH > you have > to upgrage to foo-8.0. I think that in your example, it's going to do the right thing. Instances where we allow multiple "production" versions of software (i.e. Tcl) are already differentiated by giving the port directories different names. Two things that came to mind for me: 1. Someone once made the assertion that most third-party software was installed via packages, not building ports. So we might need to handle some odd cases like only having the INDEX file, not having a ports tree at all, and so forth. (In other words, we might not have filesystem access to the Makefile that generated a package.) 2. This still doesn't solve the problem of updating dependencies. Still, I think this is an interesting idea. Bruce. PS. knu, I still have your last patch. I'm just kind of overwhelmed with work and Real Life (TM) stuff now, so I haven't been able to give it the time that it deserves. --==_Exmh_320064253P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: Xf/Ytj1uQdKmbKmu96+T2f9MQ5KaRTx3 iQA/AwUBOdoQE9jKMXFboFLDEQJV8QCg3FxoPuBQ7MQaHhznfDzVUVGfKPYAoLqY P5b/Of8I+ZVb3GM8fwblkxp7 =DpfF -----END PGP SIGNATURE----- --==_Exmh_320064253P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010031657.e93Gvtg10718>