Perhaps Some Basic Feature Requirements:
1) C compiled command line executable with full command-
line usability to: copy an installed package from one
location to another(i.e. uDOS disk to local hard drive)
given the root location of the store tree, the target tree
and manifest file.
2) Ability to remove a package given the location of the
manifest file and target tree(default=<manifest
file>/../..)
3) Ability to install/remove a *set* of manifest files
from a specified list file(or stdin) of manifest file
names, i.e. an 'install configuration'
4) Check integrity of install afterward(?)
5) Check/list dependencies
6) command line option to override dependency failsafes.
7) command line option to confirm upgrade action (udpkg
detects if package has been previously installed in
<target tree> and asks if it should be upgraded[i.e.
delete the old installed package before installing new one]
>
8) An optional curses interface to install any or
all 'install configurations' or 'manifest' files given
their directory locattionn as an argument (
'install configuration' files (possibly in XML or csv?):
1) A desciption of this configuration
2) simple text list of manifest file names. These can be
listed with full path, or the manifest path specified at
the command line as an argument (also a possible default
or system variable?)
3) optional descriptions for each manifest
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1085076
TODO list in CVS:
http://udos.cvs.sourceforge.net/udos/install/todo.txt?view=markup
Logged In: YES
user_id=262268
Some ideas for 'udpkg', the uDOS installer :)
Perhaps Some Basic Feature Requirements:
1) C compiled command line executable with full command-
line usability to: copy an installed package from one
location to another(i.e. uDOS disk to local hard drive)
given the root location of the store tree, the target tree
and manifest file.
2) Ability to remove a package given the location of the
manifest file and target tree(default=<manifest
file>/../..)
3) Ability to install/remove a *set* of manifest files
from a specified list file(or stdin) of manifest file
names, i.e. an 'install configuration'
4) Check integrity of install afterward(?)
5) Check/list dependencies
6) command line option to override dependency failsafes.
7) command line option to confirm upgrade action (udpkg
detects if package has been previously installed in
<target tree> and asks if it should be upgraded[i.e.
delete the old installed package before installing new one]
>
8) An optional curses interface to install any or
all 'install configurations' or 'manifest' files given
their directory locattionn as an argument (
'install configuration' files (possibly in XML or csv?):
1) A desciption of this configuration
2) simple text list of manifest file names. These can be
listed with full path, or the manifest path specified at
the command line as an argument (also a possible default
or system variable?)
3) optional descriptions for each manifest