Re: [ARMini-support] This machine kills pythons
- From: A Rawnsley <rcomp@xxxxxxxxxxx>
- To: armini-support@xxxxxxxxxxxxx
- Date: Thu, 12 Nov 2020 23:11:18 GMT
In message <mpro.qjpg4x00jtpc801ou.lists@xxxxxxxxxxxxxxxxxx>
Steve Fryatt <lists@xxxxxxxxxxxxxxxxxx> wrote:
On 12 Nov, A Rawnsley wrote in message
<50df5fce58.rcomp@xxxxxxxxxxxxxxxxxxx>:
I believe the Iris instructions actually explain how you can
(experimentally, so take a backup) merge your !SharedLibs by placing Iris'
copy inside a !Boot.Resources "shell" and using BootMerge to merge the
two.
Won't that completely screw up a Packman-managed SharedLibs in !Boot, by
adding/changing files without Packman knowing what's happened?
BootMerge is ROOL's recommended way of updating !Boot contents (ie. via
the Installer module), so I'd expect it to cope with it, if not, it
probably should, don't you think?
You may be right, but equally if someone with skills doesn't tackle this
"how to supply standalone software with shared libraries" dilemma (and no,
"put everything on packman and hope for automated-salvation" isn't a
solution) soon, it'll never go away.
I think perhaps the solution is a !SOmerge like !SysMerge, and maybe that
could do the necessary housekeeping to avoid such problems?
However, thinking about it, individual libraries are named by version
number, and separated by API, so unless there's something really
unpleasant going on, it shouldn't confuse PackMan because the new
libraries will be separate files. The worst that could (!?) happen would
be that Packman would re-download those files later if it thought
something else needed them (assuming they were on Packman separately).
However, we're now touching on yet another potential problem. I've seen
it suggested that every library / shared object should be a separate
package on PackMan. If so, the packman library will become almost
impossible to browse due to a deluge of libraries and other materials that
aren't actually applications in themselves. The solution to this is
probably better classification of packages and control over which ones are
actually displayed by default, so probably not the end of the world, but
certainly something like Iris uses dozens of libraries (a quick count says
well over 200, although many are symbolic links to others) which is an
*awful* lot of packages to add individually if we're going that way.
I don't know. Maybe that is the right way. Just doesn't feel very "RISC
OS" to me, and not readily compatible with a world where people still buy
software on CD and other media.
Andrew
--
R-Comp
22 Robert Moffat, High Legh, Knutsford, Cheshire WA16 6PS
Tel: 01925 755043 Fax: 01925 757377
http://www.rcomp.co.uk
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts:
