This utility is evolving really nicely,making packaging and editing of packages a easier,less time consuming task!
Editing the slack-desc file is a needed feature if you ask me,but its needed for tlz packages that were created by makepkg procedure (no configure and make)... Some apps under linux that are written in python can't be packaged by vpackager,but vpackager can have the powerful feature ,give the ability to the user to write a slack-required file and put it inside,without the need to explodepkd and makepkg again and again just to fix a typo. ( what i had to do with my last packages - fontpage and acetoneiso ).... so here my feature requests:
packageeditor should be a sepparate module of vpackager. Can you make it that,the user who starts vpackager,starts it only to package stuff,not to edit packages...no clutter with buttons that have nothing to do
with the main thing.Just include it in the file> menu,above the "quit" option)
So make package editor a sepparate module of vpackager,that can be called to open a package,just by opening the package.tlz file with it (no browse for package buttons and dialogues)
Vpackage-edit could be called from vpackager's file>edit a package menu....but it should be able to directly open tlz files with it...
and it should have the following features:
*directory listing of files inside the package (showing the dirs and the files inside)
*check if package has a proper slack-required and slack-desc file (not a must,but a sweet feature) and "slack-required" and "slack-desc" butttons that will open the files for edit, since they are always in install folder.. maybe slack-desc button could call the slack-desc editor that vpackager already has. This way the user could easily change whats written in the description,in case there are typos or old information that is absolete (old website url,wrong license,etc etc)
and if there is no slack-desc or slack-required file found inside,the user could write one (a very important feature)
*cancel,quit and apply changes buttons at the bottom =P (it will have to uncompress the package first,before the user can edit and put stuff inside,right?) Apply button should package it again and overwrite the original file.
*the ability to import file in the package (in any of the dirs it has)
*the ability to edit files (slack-required) with a text editor (i vote for mousepad,since its the fastest,but this can also be done with the preferences window,where the user can just type the command which is for the text editor,and not chose from a list or anything)...when opening a file inside the package,the user should have the ability to change it and overwrite the old file...
*the ability to create a package with makepkg out of any directory that the user choses. (maybe this could be sepparate from vpackage-edit,but it can use it --- include the option "make package from folder" in vpackagers file> menu)
the ability to import files and delete files in a package is priceless for managing packages that can't create a slack-required file and the user must write one!
Anyways,i really think that this will deliver a great support for packages that dont build with the standart procedure. Then they can be installed with a prefix to a given dir and then packaged and a slack-required file could be written for them easily.
...please don't change the way it uses the tmp directory.Its not broken,dont fix it, plus its easier for the packager to find and open the slack-desc and slack-required file of the package he/she made, so its easy to copy and paste at the forum.