@Damocles

Just seen this post after replying elsewhere.

For system updates, I've got no complaints, but I do for other software. You've made the Linux argument. Don't like RPM, use a Debian distro. Don't like that, use something else.

This is asking application developers to build their software for system x, y and z. In reality, some is built for x & y, some for z, and so on.

If the major AROS distro uses package management, then for app developers that kills two birds with one stone. 1) a standardised installer, 2) free, reliable hosting.

Those developers may not worry about offering other solutions, just a binary without an installer or just the source code, but is that the choice you mean? It's clear how that came about in Linux from the days when there weren't many users, apps or big distros. It's dangerous to offer competing solutions over different distros.

Chris

Quote:

As I pointed out in the other thread, if you don't like APM, don't use a distro(s) that use them. No one is going to force you to use them. I fail to see why the concern since this will be in limited use aimed at distro(s) wanting to use them. It's not like your going to have to use them when using the AROS SVN or AROS nightlies.

Dammy

Seriously, it seems like a much bigger discussion needs to take place before package management is deemed a good thing. See my post in the other thread. Hope nobody's offended!

Chris

You could argue using a date to identify it is essentialy a version anyhow ... but i digress.

So long as its easy to maintain and identify ... the one given is mearly an example.

Version/date should just be whatever the upstream authors use. There's no need to distinguish them or force it one way or the other.

How about <date> instead of <version>?

Dammy

AROS Package Format and Management Tools

Provide a working environment for installing, updating and maintaining Packages on AROS platforms

Package File Format
###################

Provide a suitable "Package Format" for installing and distributing AROS software. You will neeed to provide a means for storing all a packages necessary components in a single file preferably using a standard archive file format (possibly with a custom file name extension) - which must be suitable for use withing AROS.

You should provide means for packages to describe themselves, and for them to handle scripts necessary for the Package Manager and Installer to correctly utilise the packages as described below. You must idnetify and document all the components necessary to make packages work as intended.

Packages must be provided using a namespace suitable for multiple architectures and versioning..

i.e

<package>-<version>-<aros architecture>.<package format extension>

AROS-1.0-pc-i386.apm

Package Manager
###############

Must be able to check installed Packages on an AROS system (#1) and allow users to upgrade from online sources (#2) or localy stored packages. Package Installation will involve Package Manager retrieving the correct packages (or opening on disk ones where applicable), extracting them as necessary, and passing the correct scripts to the AmigaOS/AROS Installer.

Users must be able to Install, Uninstall and Validate Installations using the Package Manager.

Dependencies for packages should be handled by the Package Manager but processed via the Installer


Package Repository
##################

Implement and document a working repository for AROS software which can be utilised by the AROS Package Manager to upgrade/install components on an AROS platform.
(#2)

Packages must be identifiable for a particular platform, installable via the package manager, and should be available via applicable software categories.

Package Installation (Installer)
################################

By providing a Front end to or by updating Installer itself, enable the Installer to handle the scripts used by the AROS Package Manager. It must be able to Check Dependencies, Install, Uninstall and Validate a Package installation (check the components are correctly installed) via standard AmigaOS style Installer scripts.

#1 preferably by storing information about installed packages in a database
#2 preferably using a distributed technology such as torrents