[Top][All Lists]

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

[Octave-patch-tracker] [patch #9853] [octave forge] (image) implement ni

From: Philip Nienhuis
Subject: [Octave-patch-tracker] [patch #9853] [octave forge] (image) implement niftiread, niftiwrite, niftiinfo
Date: Fri, 5 Aug 2022 15:12:23 -0400 (EDT)

Follow-up Comment #11, patch #9853 (project octave):

Packages can have optional ("suggested") dependencies. E.g., he mapping and io
package have those [*]. And of course core Octave has plenty of them.

That the image package is "self-supporting" til now is of course Good (and
laudible, I like that); but from a practical POV I wouldn't object to
introducing suggested dependencies in any package with such a wide
functionality as the image package.
If specific dependencies for a few specific functions weren't available when
the package got built, most of the package still works and/or most users can
still use the package successfully.
Of course, the contributor of those specific functions should make sure that
missing deps. are gracefully catched during package installation and -use.

[*] maybe not formally announced, but the mapping package makes use of GDAL
and the io package has a large collection of optional Java dependencies.


Reply to this item at:


Message sent via Savannah

reply via email to

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