• MorphOS Developer
    geit
    Posts: 1030 from 2004/9/23
    There is no limitation.

    Everyone can make a database and create new entries or adapt the files included into a new database.

    All the user needs to do is adding the initial database to the database/user folder and it will automatically update and expand as it is handled and updated like a software package itself.

    There are no servers. Grunch just mimics the behavior of a user. Find a file with a higher version on given servers, download, extract and install it. All those steps are in the .db files and the manual does explain every command.

    Just ensure the files are properly tested, as they can - wanted or not - delete the entire harddrive or do what ever. The quality of the .db files also reflects the user experience. Do not overwrite already installed icons. Do not fail when removing files/folders that donĀ“t exist. De-install without forgetting any data in ENVARC: or elsewhere.

    This is nothing you should hack together in rapid fashion. It needs to be properly tested by the maintainer, which takes time.

    For a developer this is easy. They just create an drawer using the application name and having a matching icon and the application with the same name inside. Then you can basically use a single line for install and deinstall. Just name, description needs to be set.

    Once created the developer does not need to touch the entry anymore. Whenever he uploads a new archive of his software, every user will get it. Thats why developer should create their application archive from within the makefile, too. That way the archive will automatically created and will never fail.

    If there is a sloppy archive, with random names (e.g. version number in drawer, archive or application name) on each update or a different file structure or composed by hand with forgotten files, it gets hard. Same for non standard version strings.
  • »06.11.19 - 11:23
    Profile