[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57522] "pkg unload" does not care for depende

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #57522] "pkg unload" does not care for dependencies
Date: Wed, 8 Jan 2020 15:01:37 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #18, bug #57522 (project octave):

pkg.m investigates, updates and stores dependencies only when packages are
installed, uninstalled and when the database gets rebuilt. In addition it only
looks at (references) dependencies when loading packages.
To me that means that exploring, updating and and storing inverse dependencies
would ideally be at those same moments, and referencing them when unloading
would be symmetric with loading.
Dependencies and inverse dependencies both comprise static package info that
doesn't change after installation and can be safely read from the database /

But ... I realized already some time ago that when unloading a global package,
pkg.m should also look at local packages that depend on it. The other way
round probably isn't needed as I think global package shouldn't depend on
local ones in the first place. It would be daft if global packages should not
depend on local ones but nevertheless need to store inverse dependencies on
local packages in their global cache entry.
I forgot about this but now that you mention ...

So yes, there is a valid motive for on-the-fly computing of inverse
dependencies, perhaps until there's a better way of handling the global and
local package databases.
One such a way would be to simply do away with the database/cache completely
and store all dependency info more explicitly in the package's PACKINFO subdir
(i.e., not in the DESCRIPTION file). That would also simplify mxe-octave's
step of building binary packages. To that end computing dependencies on the
fly would also be handy (and needed).

Does that answer your question? (maybe it raises just more)

As to (..., "UniformOutput", false): AFAICS that isn't anywhere in the Octave
style guide, but I'll happily stick to it :-)


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]