[1186] in athena10
Re: questions on debathena-thirdparty-* conflicts and priorities
daemon@ATHENA.MIT.EDU (andrew m. boardman)
Thu Feb 19 17:54:49 2009
Message-Id: <200902192254.n1JMs0aS002574@pothole.mit.edu>
To: Alex T Prengel <alexp@MIT.EDU>
cc: "andrew m. boardman" <amb@MIT.EDU>, debathena@MIT.EDU
In-Reply-To: Your message of "Thu, 19 Feb 2009 17:03:02 EST."
<200902192203.n1JM32wm021073@dit.mit.edu>
Date: Thu, 19 Feb 2009 17:54:00 -0500
From: "andrew m. boardman" <amb@MIT.EDU>
> Well, this is a pain and confusing. I know of at least one faculty member
> who does inventor development and I'd really rather keep inventor-dev if
> at all possible. We'd really be better off if there were just one of motif
> and lesstif but obviously we need to deal with the status quo.
There's not actually too much of a conflict there; the base libraries
have different major versions and can coexist, it's just the -dev
variants that can't live with each other. Keeping libmotif3 and
motif-clients as well doesn't conflict with inventor-dev (which pulls in
lesstif2 and lesstif2-dev).
> Am I correct in presuming that if we drop libmotif-dev
> that fixes the conflicts? If yes I'd rather drop that.
Done.
> I don't know offhand if anything else in the bundle depends on libmotif-dev
> (or any other Ubuntu package, for that matter). Is there some Ubuntu package
> command option that tells that (what packages require a given package)?
It's far from perfect, but "aptitude why <packagename>" will tell you
what chain of depencies caused <packagename> to get installed, and
"aptitude why <p1> <p2>" will tell you why, assuming the installation of
<p1>, <p2> might be needed. (There's also a "why-not" argument.)
> We should punt the attach-and-run script and have the package install
> /usr/sbin/ivview. I don't recall why we had it in the first place.
We added a MIME handler (for application/x-inventor) which used it; see
source-reviewers[13456] for the gory details. We actually still have
the relevant gnome helper application in Athena 10, but removing the
attachandrun script and letting it break on private machines without the
package installed doesn't seem totally out-of-line. (I'm assuming there
will be some vaguely useful error like "can't find ivview application"
which will cause the user to (if the user cares, anyway) go through the
not-too-complicated process of finding and installing it.)
> If someone stills wants the locker version they can always do "add -f
> inventor; ivview" right?
Right.
