A discussion thread for Afterpkg
by bifferos from LinuxQuestions.org on (#5062M)
I created a new package builder/installer. It's called Afterpkg.
https://github.com/bifferos/afterpkg
I'm creating this thread to avoid protracted discussion of Afterpkg over on the "SBo scripts not building on current" sticky.
Although it can do some of the work of sbopkg and sqg Afterpkg is not really supposed to replace those, it doesn't aim for feature parity with anything else that exists.
So why?
Since I work with a lot of Python projects, I'd like to handle python package dependencies, and avoid certain problems that arise due to installpkg not understanding about pip-installed packages, and visa-versa.
I'd like to be able to make use of virtual machines to do all my image preparation, and I want my scripts to run as a normal user, pretty much anywhere, be it Windows, Linux or Mac, so I want a package builder that makes all this painless, while still being able to install builds locally as well.
What Afterpkg is not (at the moment) is a generic package management tool for your primary system, although hopefully if you use it for installing stuff it's not going to break anything! It's more for people who want to very quickly bring up a system to a given spec with minimal fuss, perhaps for deployment to the cloud, or for testing -current, or to use as a sandbox for something else.
Feel free to discuss any aspect of Afterpkg here, bugs feature requests etc...
thanks,
Biff.
https://github.com/bifferos/afterpkg
I'm creating this thread to avoid protracted discussion of Afterpkg over on the "SBo scripts not building on current" sticky.
Although it can do some of the work of sbopkg and sqg Afterpkg is not really supposed to replace those, it doesn't aim for feature parity with anything else that exists.
So why?
Since I work with a lot of Python projects, I'd like to handle python package dependencies, and avoid certain problems that arise due to installpkg not understanding about pip-installed packages, and visa-versa.
I'd like to be able to make use of virtual machines to do all my image preparation, and I want my scripts to run as a normal user, pretty much anywhere, be it Windows, Linux or Mac, so I want a package builder that makes all this painless, while still being able to install builds locally as well.
What Afterpkg is not (at the moment) is a generic package management tool for your primary system, although hopefully if you use it for installing stuff it's not going to break anything! It's more for people who want to very quickly bring up a system to a given spec with minimal fuss, perhaps for deployment to the cloud, or for testing -current, or to use as a sandbox for something else.
Feel free to discuss any aspect of Afterpkg here, bugs feature requests etc...
thanks,
Biff.