Feedback from component (suite?) vendors

From: Andy Neillans [ABCC Computers] (andy_at_abcc-computers.co.uk)
Date: 07/11/04 

Date: Sun, 11 Jul 2004 21:51:58 +0100

Hi all,

Am currently toying with adding component installation into our product,
Package Manager (www.abccweb.co.uk/products/PackMan/), which I can see
working like:

- Component Vendor organises their source into a directory (not restricted
to source only, could be dcu's or both!)
- Runs some program, specifies the directory to package. It then compresses
and encrypts the source files, with an optional installation password (that
the customer would need to key in in order for Package Manager to actually
unpack and install the component(s)).
 Vendor can specify:
 - Default install path
 - Compilation steps (if any, and the ability to run these steps after
installation)
 - Package List modification

The end user would simply download and double click the file (assuming they
had Package Manager installed) -- they would be prompted to see where they
wanted it unpacked to, and for the password - if any. Installation from that
point is automatic, along with any modifications to package lists, library
path etc (all set by the component vendor).

Why? It would certainly clear up a lot of 'how do I install xyz suite?' type
issues!

The 'build' program would be distributed to vendors freely.

Any comments / feedback?

Andy

Relevant Pages

  • Re: etch help
    ... followed your directions but got nowhere. ... screen so things like "would not select for installation" may make ... can't figure out how to use the package manager or how to properly ... It will help you get better response from the list. ...
    (Debian-User)
  • Re: etch help
    ... could not mark all for installation or update ... package manager and did the search some of the options would not ...
    (Debian-User)
  • Re: A real package manager in action
    ... It's already more hard work for the user than a package manager would ... resource is missing it sets a flag in a system variable. ... Why not let the maintainer write the dependency file after all you ... All this can be done now and if you opt for manual installation ...
    (comp.sys.acorn.apps)
  • Re: A real package manager in action
    ... All the abovenamed resources should be present in!Boot somewhere. ... I'd also argue that we've lasted long enough with the installation method we currently have to suggest it's probably not broken enough to require fixing. ... a package manager which replaces AMPlayer whilst it's still running is probably outside the scope of its design... ... You might do better with an 'upgrade checker' program, which doesn't handle the installation procedure, or some other semi-measure or rigid structure. ...
    (comp.sys.acorn.apps)
  • Re: A real package manager in action
    ... It's already more hard work for the user than a package manager would ... doesn't have tell you or carry links to resources. ... All this can be done now and if you opt for manual installation ... The program still has to identify its dependencies so the programmer ...
    (comp.sys.acorn.apps)