Re: [ARMini-support] Harddisc strucure
- From: Chris Hall <chris@xxxxxxxxxx>
- To: <armini-support@xxxxxxxxxxxxx>
- Date: Fri, 08 Apr 2016 10:22:25 +0100
In message <ffe9226d55.boase@xxxxxxxxxxxxxxxxx>
Bernard Boase <b.boase@xxxxxxx> wrote:
[Splitting this thread away from "ARMX6 OS update 7 released"]
On 7 Apr, john@xxxxxxxxxxxxxxxx typed:
I kept that structure on all subsequent machines up to Iyonix, but
when moving stuff over to ARMX6 (checking each item individually to
see whether it worked, rather than just bulk copying) the distinction
between Apps and Utils in terms of either 'weight', frequency of use
or anything else seemed so blurred that I put everything from both
into structured directories within Apps (not the 'Utilities' though).
I have evolved something similar over the years. But I find no use for
a category Utilities: it's meaningless. All programs have _some_ area
of application and can be categorised accordingly.
I find that Apps is useful for things that you usually want to run
(like !ChangeFSI) yourself and Utilities is useful for things that you
want to run when you double-click on a particular filetype but don't
normally need to run otherwise. That makes things you want to run
yourself easily findable in Resources:$.Apps as Utilities is always
looked at at Boot.
I use sub directories within Apps and Utilities (like 'Impression') to
hold the zip files, examples files, help and documentation that came
with each version as well as the various versions of the App in
directories like 'Imp567' or whatever (so they are not seen unless you
want them to be). So I would not like some external software like
PackMan to make assumptions here...
The sub directories are effectively invisible (to Resources:$.Apps)
thank goodness and I only open them when I have a new version of some
software to install. That way I can easily revert to the previous
version if I need to.
--
Chris Hall <chris@xxxxxxxxxx>
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts: