Re: Official Package Manager
Posted: 12 Oct 2011, 03:09
Porteus Package Manager2 has arrived. I am just having it cleaned and polished before releasing it for testing. It is far from perfect; however it does have some major improvements over the existing version. At the moment dependency resolution does not work solid for ALL third party repos, but it will get better. It is primarily to be used for getting modules from the official porteus server, or converting slackware packages. In this manner, most, if not all dependencies will be resolved. It weighs in at under 300Kb which is great for such a large script and keeps in line with our minimal size ideaology.
FEATURES:
Dependency resolution: across Porteus and slackware repos.
Activation: When you activate a module, its deps are found and activated. If deps don't exist they are resolved.
Deactivation: Deps of module being deactivated are found, and if not being used by another app, are also deactivated.
Config file editing: This allows you to change repo URL's or remove config files.
Rootcopy support: If PPM senses you are using 'always fresh' mode it can palce config files into rootcopy.
Package browse or search by keywords: Allows you to search for 'image editor' or similar.
Module merger: I don't support it. But i included a module merger for people that prefer one single module with all deps included.
Third party repos: Chakra, Salix, Debian, Fedora, Fidoslax, Slackbuilds, Slacky
Fedora is currently dormant and stops short of downloading the package. I think the process of generating the menus is too time consuming and am thinking about dropping Fedora from the final version. I left it in place to get opinions. Should it stay or should it go?
Slackware converter
You can convert from a slackware ISO, a local slackware file, a folder full of slackware packages or use the online repo's. Packages are converted and placed in your chosen storage. When you attempt to activate them, all deps will be resolved (hopefully).
Slackbuilds
Allows you to sync a slackbuilds repository locally after which you can browse the packages, select one, download it and build it locally on your system. You will need to watch the build output to ensure the build was successful. Advanced users can also edit the .slackbuild file or just download the source to do with as they please. If you don't want to sync, you can just use the online express repo and download a package source to build as you like.
TODO:
Add a library finder. I currently use a script that allows me to enter a library, and it will go and search across multiple distro repositories until it finds the package that contain the library i need. It then converts the package into a Porteus compliant module. I will add this to the next PPM.
Tidy up dependency resolution for 3rd party apps.
This project has been an epic saga for me ... at times very frustrating and it has taken me away from maintaining 32bit Porteus (which i enjoy). It may be that not many more NEW features are added and i spend a little time just refining what i already have. As usual constructive comments are welcome, as long as they don't require me to spend months working or rewriting this animal.
Once i have cleaned it up a little i will release the 32bit version for testing. During this time i will be road testing the 64bit version and fixing any bugs that appear.
FEATURES:
Dependency resolution: across Porteus and slackware repos.
Activation: When you activate a module, its deps are found and activated. If deps don't exist they are resolved.
Deactivation: Deps of module being deactivated are found, and if not being used by another app, are also deactivated.
Config file editing: This allows you to change repo URL's or remove config files.
Rootcopy support: If PPM senses you are using 'always fresh' mode it can palce config files into rootcopy.
Package browse or search by keywords: Allows you to search for 'image editor' or similar.
Module merger: I don't support it. But i included a module merger for people that prefer one single module with all deps included.
Third party repos: Chakra, Salix, Debian, Fedora, Fidoslax, Slackbuilds, Slacky
Fedora is currently dormant and stops short of downloading the package. I think the process of generating the menus is too time consuming and am thinking about dropping Fedora from the final version. I left it in place to get opinions. Should it stay or should it go?
Slackware converter
You can convert from a slackware ISO, a local slackware file, a folder full of slackware packages or use the online repo's. Packages are converted and placed in your chosen storage. When you attempt to activate them, all deps will be resolved (hopefully).
Slackbuilds
Allows you to sync a slackbuilds repository locally after which you can browse the packages, select one, download it and build it locally on your system. You will need to watch the build output to ensure the build was successful. Advanced users can also edit the .slackbuild file or just download the source to do with as they please. If you don't want to sync, you can just use the online express repo and download a package source to build as you like.
TODO:
Add a library finder. I currently use a script that allows me to enter a library, and it will go and search across multiple distro repositories until it finds the package that contain the library i need. It then converts the package into a Porteus compliant module. I will add this to the next PPM.
Tidy up dependency resolution for 3rd party apps.
This project has been an epic saga for me ... at times very frustrating and it has taken me away from maintaining 32bit Porteus (which i enjoy). It may be that not many more NEW features are added and i spend a little time just refining what i already have. As usual constructive comments are welcome, as long as they don't require me to spend months working or rewriting this animal.
Once i have cleaned it up a little i will release the 32bit version for testing. During this time i will be road testing the 64bit version and fixing any bugs that appear.