Files changed (1)
+A long time ago I started developing this idea of a linux application to help newcomers install new applications to their linux systems even if they had no idea how the process is actually done. The initial result was an interactive bash script that the user could launch and answer a few questions, after which their new application would be compiled.
+The application proved to be useful, so I decided to learn gambas to create a graphical interface that did the same thing. This produced a nice GUI and even added support for building from cruxports4slack. The gambas gui works, but I always felt it could be improved. And so the story continues...
+New development of the application is now being done in python. Python offers great support for most things vpackager does, along with gtk integration and threading support which turn this thing into a really nice, useful application while keeping it really small.
+The goal for this application has always been to help newcomers easily install new applications on their systems. At the same time, the new development branch also puts more focus aiding packagers for the project and thus speed up the process of building applications to host in the distro's repositories. Here is how it works.
+To standadize as much as possible, vpackager relies on sbbuilder, a tool written to generate build scripts for several source types. By doing this, vpackager is able to easily build just about any application while at the same time produce a package and source tree that meets the requirements for submission to the online repositories.
+Furthermore, vpackager extends sbbuilder by automatically detecting the source type to be built and generating the appropriate script (limited to local source archives only). For source archives to be downloaded, the user can specify a source type if necessary and still generate the appropriate script.
+Coupled with sbbuilder, vpackager uses a sqlite3 database backend for job queueing and to keep a history of built packages. This allows the user to build a series of packages at once. The to-do list is stored in the database, and vpackages launches a worker process that queries this database going down the list one by one.