Date: Tue, 29 Feb 2000 11:10:48 GMT From: Salvo Bartolotta <bartequi@neomedia.it> To: Walter Brameld <brameld@twave.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re Complex interdependent [meta]ports (was Re: Gnome Install) Message-ID: <20000229.11104800@bartequi.ottodomain.org> In-Reply-To: <00022818593701.00658@Bozo_3.BozoLand.domain> References: <00022818593701.00658@Bozo_3.BozoLand.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 2/29/00, 12:38:58 AM, Walter Brameld <brameld@twave.net> wrote=20 regarding Gnome Install: > Was just curious if the person asking earlier was able to finally > install Gnome. I decided to try it just to see if it would work (Well > yes, as a matter of fact I AM bored!). > When it reached the point of installing gnomeprint, it failed with the= > message "-lungif - no such file or directory". libungif was shown as a= > dependancy and the install claimed it as "found" when in fact it was > not installed on my system. > Next stop: gmake[2] gave a failure when trying to compile parsef.c or > some such. This was cured by de-installing and installing gmake! > It just now finished (this sucker must download about 50 meg!) without= > any further errors. > I don't do a lot of fiddling with my system, and I guess I'm just > curious as to how it could have gotten into this state. As for the > person installing gnome, watch the errors and do some back-checking. > Apparently some rather peculiar conditions can cause it to fail. > -- Walter Brameld > in=B7tel=B7lec=B7tu=B7al > n. Someone who has been educated past his/her level of intelligence. > Join the Army, meet interesting people, kill them. Dear Walter, Last week, I met (by and large) analogous problems when dealing with=20 such mega "metaports". I tried to install KDE11-i18n-1.1.2, just to=20 play with Russian etc. locales in a more "international" fashion (or,=20 if you prefer, "context"). The first installation produced no (apparent) errors; however,=20 KDE-i18n did NOT operate properly. The next day, I cvsupped the ports=20 tree , and installed (again, as a port) the new version of qt-i18n=20 (1.44b) -- after making clean and pkg_deleting the previous version of=20 that toolkit. =20 The remedy was worse than the disease. A moment's thought suggested a drastic but effective solution: i) suitably grep e.g. the metaport installation log, extracting the=20 directories of the ports as well as the packages installed; of course,=20 you can also directly obtain the dependency list via the ports=20 mechanism (pretty-print-build-depends-list target ...);=20 ii) create a simple script pkg_deleting -f **all** of the KDE-related=20 packages, and cleaning the corresponding ports (ie issuing "make=20 clean" in their directories); iii) reinstall the KDE11-i18n port. Needless to say, it behaves well enough now -- although it took its=20 time to compile and install. Incidentally, the Japanese locale is=20 somehow slow on my PIII 450 Mhz 384 MB RAM -- probably (?) because of=20 the time it takes to draw Japanese "pictures"; on the other hand, the=20 Russian locale (ya gavaryoo pa-rooskee ;-) , which is much more=20 responsive, takes a little time to open, say, a 2MB HTML file. =20 I seem to understand that, when such complex dependencies are=20 involved, an updated [meta]port may imply overall interwoven=20 (interrelated) modifications: simply pkg_deleting and remaking the=20 port for *just* one package in the [meta]port, in general, may NOT=20 work. Those modifications are only included if you rebuild **all** of=20 the relevant [meta]port components. Unless I have completely misunderstood it, and I have made an awful=20 blunder ... =20 Best regards Salvo =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000229.11104800>