Date: Wed, 20 Jun 2001 12:10:42 -0400 From: "Antoine Beaupre (LMC)" <Antoine.Beaupre@ericsson.ca> To: Jordan Hubbard <jkh@osd.bsdi.com> Cc: "Antoine Beaupre (LMC)" <Antoine.Beaupre@lmc.ericsson.se>, alex@big.endian.de, jhb@FreeBSD.ORG, richy@apple.com, libh@FreeBSD.ORG, will@physics.purdue.edu Subject: Re: packagetool.tcl Message-ID: <3B30CB02.2000700@lmc.ericsson.se> References: <20010619231951.B4230@zerogravity.kawo2.rwth-aachen.d> <20010619142832K.jkh@osd.bsdi.com> <3B30B1E4.80909@lmc.ericsson.se> <20010620084827V.jkh@osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan Hubbard wrote: > From: "Antoine Beaupre (LMC)" <Antoine.Beaupre@ericsson.ca> > Subject: Re: packagetool.tcl > Date: Wed, 20 Jun 2001 10:23:32 -0400 > > >>Of course. But we don't want that. What we want is *libh* to be >>expressive enough to understand plists. :) >> > > Erm, this is a bit like those folks who think that you can improve the > sound quality of really old recordings by somehow applying enough > modern digital sound processing. If the data you need just isn't > there to begin with, it becomes awfully hard to pull it out of thin > air. :) <off-topic type=delirium> Well, you can! With our new gizmo-sound-processing-super-digital-airwave-processor, your old gramophone recordings will sound as good as any modern digital studio recording! Yeah. Right. ;) Seriously, I still saw a few filters that could do marvels with these old scratchy vinyls. Removes the hiss and the clicks quite well. But of course, the thing won't do any good on that 20-year old black sabbath vinyl lying in the 10 year old dead-lizard box. :) </offtopic> > That's the point I'm trying to make here. libh contains a lot > more information about a package, such as whether it occludes or > updates another package, and this information goes straight into the > new registration database. Hmm... Yes... Of course, you're right. I haven't though of that "package registry integrity" thing. :) I'm just getting used to libh, now.. Don't flame me. :) > If the old package doesn't provide it, and > they won't since we didn't even make provisions for stuff like that > back then, what you're left with post-installation is still something > that doesn't stand up to the installation of a modern package. As you > get into this, I'm sure you'll discover even worse "gotchas" than > this. Of course. But what's the alternative here? You talked about offering the user to still use pkg_add. Isn't that worse? Wouldn't that clobber the existing libh installs? >>I'm not sure I follow you here. We don't want the old package system to >>be compatible with the new one. But we would probably want the new one >>to be compatible with the old one, ie. that it could at least >>*understand* it. > > I'm sure it's capable of "understanding" it just fine, it just may not > find the old packages expressive enough for its needs. Yes, I understand the value of that point now. > Why not wait until libh is fully fleshed out in any case before tackling > the thorny backwards-compatibility issues? Hmm... Because it might be a good idea to include backward compatibility as an objective of libh... But I don't think it is, was, or will really be. :) Anyways, I guess I'm really talking for nothing here since I haven't coded a single line in there yet. Let's wait (or code!) for that shiny new libh. :) I guess that if the design is modular enough (as I think it is), we won't have problems implementing as much backward compatibility as possible. >>This shouldn't be a problem. I tried to implement a hacky perl script to >>cleanup /var/db/pkg of duplicate packages that parsed +CONTENTS files >>and I found that in most cases, the lines are quite simple. The >>"@-directives" are not that common. > > That's fine, but it's the uncommon cases I'm talking about here. Ok. cheers, A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:antoine.beaupre@ericsson.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B30CB02.2000700>