A package/software manager for Visopsys
Posted: Thu Dec 29, 2016 1:00 pm
I have created this post to talk about the package/software manager for Visopsys. Maybe you need/want to read first http://visopsys.org/forums/viewtopic.ph ... 0&start=10.
I will show my original idea for the package manager, and then we can discuss about that idea (and change it, of course). My idea is to make the following components, to get finally a “software manager” and all we need:
- 'Visospys Package Manager' (vpm for friends): The package manager is use just to install and uninstall packages. (I think it's a bit similar to 'dpkg' on Debian). We must have a “installed packages database” (a simple txt file can be use).
Example of hypothetical use:
(Install my_package): vpm my_package.zip
(Uninstall my_package): vpm -r my_package
- Another software to download the packages from the server or repo (I haven't got a name for this yet ): This should get the packages and it dependencies or whatever them need and execute/call “vpm” to install the packages into the system.
- The “software manager”: This should be the graphical interface, and simple to use. In this you will get information about the different software available and you will be able to install and uninstall software. To do this, the software manager will call vpm and the other -unnamed- software. Maybe in the future we can add things like “user ratings”.
Also we will need:
- A software/package repository: Maybe a simple FTP/HTTP server at visopsys.org (like archive.visopsys.org or software.visopsys.org) or maybe a Git repo at Github in which all the users can make 'Pull requests' to add new software to the repo (Of course it will be controled by Andy, I think). I think all the people have to be able to create their own repo, so it's necesary to make an “standard” for this.
- Packages: I think that our packages should be just ZIP files, that contains the binaries of the software, configuration, images, doc, etc. Also the packages should contain a config file for vpm.
P.D.: I have written a bit of the code of vpm, but just to treat the arguments.
I will show my original idea for the package manager, and then we can discuss about that idea (and change it, of course). My idea is to make the following components, to get finally a “software manager” and all we need:
- 'Visospys Package Manager' (vpm for friends): The package manager is use just to install and uninstall packages. (I think it's a bit similar to 'dpkg' on Debian). We must have a “installed packages database” (a simple txt file can be use).
Example of hypothetical use:
(Install my_package): vpm my_package.zip
(Uninstall my_package): vpm -r my_package
- Another software to download the packages from the server or repo (I haven't got a name for this yet ): This should get the packages and it dependencies or whatever them need and execute/call “vpm” to install the packages into the system.
- The “software manager”: This should be the graphical interface, and simple to use. In this you will get information about the different software available and you will be able to install and uninstall software. To do this, the software manager will call vpm and the other -unnamed- software. Maybe in the future we can add things like “user ratings”.
Also we will need:
- A software/package repository: Maybe a simple FTP/HTTP server at visopsys.org (like archive.visopsys.org or software.visopsys.org) or maybe a Git repo at Github in which all the users can make 'Pull requests' to add new software to the repo (Of course it will be controled by Andy, I think). I think all the people have to be able to create their own repo, so it's necesary to make an “standard” for this.
- Packages: I think that our packages should be just ZIP files, that contains the binaries of the software, configuration, images, doc, etc. Also the packages should contain a config file for vpm.
P.D.: I have written a bit of the code of vpm, but just to treat the arguments.