Re: pkg scripts/dependency issues

2002-01-10 Thread Dimitri Maziuk
* 'cduck' Chris Grierson ([EMAIL PROTECTED]) spake thusly: ... 'dpkg *.deb' will install packages in the correct order > *so as to satisfy dependencies*, but that isn't the issue. the issue is > whether the 'preinst' scripts should be checking for installation status > of a package by means of eit

Re: pkg scripts/dependency issues

2002-01-10 Thread 'cduck' Chris Grierson
On Thu, 10 Jan 2002, Dimitri Maziuk wrote: > * 'cduck' Chris Grierson ([EMAIL PROTECTED]) spake thusly: > ... > > > > i think you misunderstood my intention. i wasn't trying to veil a > > complaint, > > rather ascertain the proper way to mass-install a large list of packages w/o > > encountering

Re: pkg scripts/dependency issues

2002-01-10 Thread Dimitri Maziuk
* 'cduck' Chris Grierson ([EMAIL PROTECTED]) spake thusly: ... > > i think you misunderstood my intention. i wasn't trying to veil a complaint, > rather ascertain the proper way to mass-install a large list of packages w/o > encountering the problem of not packages install various files/links/dir

Re: pkg scripts/dependency issues

2002-01-10 Thread 'cduck' Chris Grierson
On Wed, 9 Jan 2002, Dimitri Maziuk wrote: > * 'cduck' Chris Grierson ([EMAIL PROTECTED]) spake thusly: > ... > > what my real concern is, is whether or not my entire system is mangled > > because of situations like this -- i generally have my systems installed > > via snagging a list of packages f

Re: pkg scripts/dependency issues

2002-01-09 Thread Dimitri Maziuk
* 'cduck' Chris Grierson ([EMAIL PROTECTED]) spake thusly: ... > what my real concern is, is whether or not my entire system is mangled > because of situations like this -- i generally have my systems installed > via snagging a list of packages from one machine and installing them all > at the same

pkg scripts/dependency issues

2002-01-09 Thread 'cduck' Chris Grierson
i know for sure that when j2sdk1.3 was installed the first time, it did not create the link in /usr/lib/mozilla for the java plugin. purging that package (j2sdk1.3), and reinstalling it resulted in the missing link (no pun). i am assuming this could have been the case because mozilla was not inst