Pkg - CLI package manager
- Max Headroom
- Posts: 421
- Joined: Wed 28 Jun 2006, 07:17
- Location: GodZone Kiwi
- Contact:
G'day sc0ttman, I've been Directed 2 your cli Package Manager in the Hope that it can Resolve Missing Python ( among Other ) Dependencies when Trying 2 install Compiz & VLC w/ the Std Native Puppy Package Manager in LxPup Bionic 18.05 on an HP Compaq NC8230, 1.73 GHz intel Centrino CPU, 2 GB RAMemory, ATI Radeon X600 Graphix. Frugal install Dual Booting w/ M$ Virus Magnet Windows
However My cli aRe rather Basic & I Need Help installing your cli Package Manager, Please ;-)K
However My cli aRe rather Basic & I Need Help installing your cli Package Manager, Please ;-)K
- Attachments
-
- Screenshot.png
- (151.8 KiB) Downloaded 360 times
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!
cd into the Pkg-master folder, and THEN run the installer...
Sorry, it's a crappy, simplistic installer script..
Sorry, it's a crappy, simplistic installer script..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
- Max Headroom
- Posts: 421
- Joined: Wed 28 Jun 2006, 07:17
- Location: GodZone Kiwi
- Contact:
G'day sc0ttman, I'm Sorry but it's still not working? What am I doing wRong?, Please...
;-(K
;-(K
- Attachments
-
- Screenshot2.png
- (136.96 KiB) Downloaded 342 times
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!
I could suggest other ways to install ... But I'll tell you where you went wrong, in case you care...
You typed:
cd /Pkg-master
but you should have typed (no leading slash):
cd Pkg-master
or (also works):
cd /root/Pkg-master
The reason it didn't work for you is because "cd /Pkg-master" expects the Pkg-master folder to exist at / (the very top level).
..But it's inside the /root folder... hence the latter two commands work...
Then ... once you got inside the /root/Pkg-master folder, you ran
installer.sh
... you tried to run the script but didnt give any path, only the filename (by default your terminal looks for comands with no path in /usr/bin/, /usr/local/bin/ and a bunch of other places where commands (like 'cd') live.. It's called the $PATH)... But in this case it couldn't find installer.sh, cos it's not in your $PATH, it's in the current dir...
To fix your input, simply give the path, which in your case, at that point, was the current dir (represented by a dot):
./installer.sh
... that should do it... Using ./something means something in the current dir...
[...confusingly the 'cd' command (and others) don't need ./ to find stuff in the current dir, but when executing commands or scripts directly in the terminal itself (running Bash), then you do need to use ./ to execute stuff in the current dir, else it will look in $PATH]
I will get around to making a more up to date PET at some point, which
would be easier to install...
Or... last resort, you can *probably* use ROX to highlight all the folders in Pkg-master, then drag and copy to / ... That might also work..
... Hopefully that is all clear as mud
You typed:
cd /Pkg-master
but you should have typed (no leading slash):
cd Pkg-master
or (also works):
cd /root/Pkg-master
The reason it didn't work for you is because "cd /Pkg-master" expects the Pkg-master folder to exist at / (the very top level).
..But it's inside the /root folder... hence the latter two commands work...
Then ... once you got inside the /root/Pkg-master folder, you ran
installer.sh
... you tried to run the script but didnt give any path, only the filename (by default your terminal looks for comands with no path in /usr/bin/, /usr/local/bin/ and a bunch of other places where commands (like 'cd') live.. It's called the $PATH)... But in this case it couldn't find installer.sh, cos it's not in your $PATH, it's in the current dir...
To fix your input, simply give the path, which in your case, at that point, was the current dir (represented by a dot):
./installer.sh
... that should do it... Using ./something means something in the current dir...
[...confusingly the 'cd' command (and others) don't need ./ to find stuff in the current dir, but when executing commands or scripts directly in the terminal itself (running Bash), then you do need to use ./ to execute stuff in the current dir, else it will look in $PATH]
I will get around to making a more up to date PET at some point, which
would be easier to install...
Or... last resort, you can *probably* use ROX to highlight all the folders in Pkg-master, then drag and copy to / ... That might also work..
... Hopefully that is all clear as mud
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
- Max Headroom
- Posts: 421
- Joined: Wed 28 Jun 2006, 07:17
- Location: GodZone Kiwi
- Contact:
Thanx sc0ttman 4 your support... Clear as Mud indeed! ;-\
Thanx 2 yoU, I've Successfully installed your cli Package Manager, which then Successfully installed VLC, Testes Working!
But unfortunately Compiz still isn't working... ? I don't understand the Error
Thanx 2 yoU, I've Successfully installed your cli Package Manager, which then Successfully installed VLC, Testes Working!
But unfortunately Compiz still isn't working... ? I don't understand the Error
- Attachments
-
- Screenshot3.png
- (177.65 KiB) Downloaded 348 times
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!
at last...
Sorry ... I dont know anything about Compiz... You could post in the Users (for the regulars) section ...
-------------------
Somewhat related to the above post about working with local files..
I have finally fixed TAB completion for local files and dirs in the latest Pkg
and
Basically, whenever working with local files, Pkg TAB completion will work much better.. especially if you start with ./ or ../ when TABbing to complete dirs & files
This makes Pkg much nicer to work with when checking, converting, installing (etc) local files - cos you can complete long pkg names and traverse long dir names so much easier (just hit TAB)..
------------
Pkg still keeps it's custom, context-sensitive TAB completion too...
Example, if you type
you will get a list of all repos auto completed (not local files and dirs)..
And if you do
you will get a list of all installed packages (not local files or dirs)
And if you do
you will get available gimp packages listed from your repos
...etc..
As far as I am aware, there are not many (if any) other package managers out there with this cool, context-sensitive TAB completion - Pkg can now auto-complete files & dirs properly (like most commands), but also (auto filtered) package names, repo names, build scripts, as well as its own commands & options, and more.
-------------------
Somewhat related to the above post about working with local files..
I have finally fixed TAB completion for local files and dirs in the latest Pkg
Code: Select all
pkg <command> ./path/to/local/file
Code: Select all
pkg <command> ../path/to/local/file
This makes Pkg much nicer to work with when checking, converting, installing (etc) local files - cos you can complete long pkg names and traverse long dir names so much easier (just hit TAB)..
------------
Pkg still keeps it's custom, context-sensitive TAB completion too...
Example, if you type
Code: Select all
pkg repo-list [TAB]
And if you do
Code: Select all
pkg uninstall [TAB]
And if you do
Code: Select all
pkg add gimp[TAB]
...etc..
As far as I am aware, there are not many (if any) other package managers out there with this cool, context-sensitive TAB completion - Pkg can now auto-complete files & dirs properly (like most commands), but also (auto filtered) package names, repo names, build scripts, as well as its own commands & options, and more.
Last edited by sc0ttman on Sun 18 Nov 2018, 16:15, edited 1 time in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Pkg to 1.9.22
I've updated Pkg to 1.9.22
I have also added an updated PET to the first post for easier download/install:
Download link:
http://www.murga-linux.com/puppy/viewto ... &id=120124
Pkg is in a pretty good place at the moment, hence the versioned release...
I have also added an updated PET to the first post for easier download/install:
Download link:
http://www.murga-linux.com/puppy/viewto ... &id=120124
Pkg is in a pretty good place at the moment, hence the versioned release...
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Any way to get the GUI to startup in a bigger window so the description is visible?
looking like this:
looking like this:
- Attachments
-
- capture20272.jpg
- Make it start like this
- (52.11 KiB) Downloaded 693 times
-
- capture20968.png
- As it now starts
- (47.85 KiB) Downloaded 693 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
You could update your JWM settings in ~/.jwm/jwmrc-personal to fix the dimensions.
Or hack /usr/sbin/gpkgdialog (look for a line that has gtkdialog in it, around there somewhere, adjust the height="" and width="" bits)
----------------------
I've done some updates and fixes for Pkg since releasing the 1.9.22 PET ..
(available on Gitlab)
I've done some fixes for the commands:
The fixes, some of which only affect .deb based Pups, include:
- fix handling of libs: respect /usr/lib/i386-linux-gnu symlinks (also i486/i586/i686 and amd64)
- fixes failure to handle package names with various suffixes
- fixes failure to sometimes find the right file
- fix - delete downloaded packages once they're no longer needed
- fixes in creation of a single, combined pinstall.sh file
- fixes in output messages (removed outdated commands, and more)
- fixes in `pkg install <sfs-file>` and `pkg uninstall <sfs-file>`
So now, the following work fine for me on Puppy Stretch 7.5 (based on Debian):
.. the 2 commands above should now produce working SFS files of the Gimp and Kodi on any .deb based Puppies
Also, the following commmands should now work OK for loading/unloading SFS files:
(Pkg will detect they are SFS files and (un)mount them as needed... So now Pkg is a bit better at handling SFS files as native packages )
If the SFS files you created are in ~/pkg/ (the default Pkg work dir), then, even simpler, you can just do this:
For example:
(will install the GIMP SFS package, if it's found in ~/pkg/)
...Also, I updated command_not_handle.sh to show local packages too..
So when you run a command that is not found, you will see something like this - with matching local packages now suggested too:
(I tested the above stuff by building Blender, Gimp, OpenArena, Nexuiz and Kodi SFS files, all of which ran OK after install after these fixes )
Or hack /usr/sbin/gpkgdialog (look for a line that has gtkdialog in it, around there somewhere, adjust the height="" and width="" bits)
----------------------
I've done some updates and fixes for Pkg since releasing the 1.9.22 PET ..
(available on Gitlab)
I've done some fixes for the commands:
Code: Select all
pkg sfs-combine <pkg-name>
Code: Select all
pkg pkg-combine <pkg-name>
- fix handling of libs: respect /usr/lib/i386-linux-gnu symlinks (also i486/i586/i686 and amd64)
- fixes failure to handle package names with various suffixes
- fixes failure to sometimes find the right file
- fix - delete downloaded packages once they're no longer needed
- fixes in creation of a single, combined pinstall.sh file
- fixes in output messages (removed outdated commands, and more)
- fixes in `pkg install <sfs-file>` and `pkg uninstall <sfs-file>`
So now, the following work fine for me on Puppy Stretch 7.5 (based on Debian):
Code: Select all
pkg sfs-combine gimp
Code: Select all
pkg sfs-combine kodi
Also, the following commmands should now work OK for loading/unloading SFS files:
Code: Select all
pkg install /path/to/some.sfs
Code: Select all
pkg uninstall /path/to/some.sfs
If the SFS files you created are in ~/pkg/ (the default Pkg work dir), then, even simpler, you can just do this:
Code: Select all
pkg install <package-name>
Code: Select all
pkg uninstall <package-name>
Code: Select all
pkg install gimp
...Also, I updated command_not_handle.sh to show local packages too..
So when you run a command that is not found, you will see something like this - with matching local packages now suggested too:
Code: Select all
# kodi
The 'kodi' command might be available in the following packages:
kodi_17.1+dfsg1-3
You can install it with the following command:
pkg add kodi
These local packages may also be a match:
kodi_17.1+dfsg1-3-WITHDEPS_stretch_7.5.sfs
Last edited by sc0ttman on Tue 04 Dec 2018, 00:42, edited 2 times in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
new commands: add-repo, rm-repo
I've added two new, pretty cool commands:
pkg add-repo - add a third-party Ubuntu, Debian or Slackware repo
pkg rm-repo - remove/uninstall any user-added repo
... now adding more repos to your Puppy will be easier than ever!
Now available in the latest Pkg
Adding a repo:
...to see more help and info, just type:
or
You will get:
EDIT [29th Nov]: bugfixed the above commands, and the installer - which will no longer remove any repos you added yourself upon (re)installation..
pkg add-repo - add a third-party Ubuntu, Debian or Slackware repo
pkg rm-repo - remove/uninstall any user-added repo
... now adding more repos to your Puppy will be easier than ever!
Now available in the latest Pkg
Adding a repo:
Code: Select all
pkg add-repo <repo-name|repo-url> [distro] [distro-version] [repo-stream(s)]
Code: Select all
pkg add-repo
Code: Select all
pkg usage add-repo
Code: Select all
# pkg usage add-repo
Usage: pkg add-repo <repo-name|repo-url> [distro] [distro-version] [repo-stream(s)]
Creates a Puppy-compatible repo file from a third-party PPA (Ubuntu), Debian or Slackware repo.
** For Launchpad PPA or Ubuntu third-party repos:
pkg add-repo ppa:<user>/<repo> [debian|ubuntu] [bionic|stretch|artful|etc] [main,all,contrib,non-free,etc]
Examples:
pkg add-repo ppa:team-xbmc/ppa
pkg add-repo ppa:team-xbmc/ppa ubuntu bionic
pkg add-repo ppa:team-xbmc/ppa ubuntu artful
pkg add-repo ppa:team-xbmc/ppa debian stretch
** For third-party Debian repos:
pkg add-repo http://site.com/[debian|ubuntu]/ [stretch|bionic|etc] [main,contrib,non-free,etc]
Examples:
pkg add-repo http://rpms.litespeedtech.com/debian/
pkg add-repo http://rpms.litespeedtech.com/debian/ stretch main
pkg add-repo http://repo.steampowered.com/steam/ precise steam
pkg add-repo http://http.kali.org/kali/ kali-bleeding-edge main contrib non-free
NOTE: Any ommitted distro names, distro versions or repo streams will be guessed.
** For third-party Slackware repos:
pkg add-repo <repo-url>
Examples:
pkg add-repo https://rlworkman.net/pkgs/14.2/PACKAGES.TXT.gz
pkg add-repo https://packages.slackonly.com/pub/packages/14.2-x86/PACKAGES.TXT.gz
NOTE: Slackware repos must end with PACKAGES.TXT or PACKAGES.TXT.gz
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
I know there doesn't seem to be much interest in Pkg, so it's unlikely anyone will wanna help out with it, but here are a few features I wanna add (just FYI):
New syntax for combining packages: pkg combine <pkgname> --sfs|--pet|--deb|--txz|--tgz
(https://gitlab.com/sc0ttj/Pkg/issues/22)
Plugin system:
(https://gitlab.com/sc0ttj/Pkg/issues/13)
If there are any other things people want or need from Pkg, let me know..
If you wanna help out with Pkg, making it more 'woof2' compatible would be nice...
The end goal being that Pkg can help woof build no X puppies.. or be integrated into woof2.. or used as remaster tool..
At some point I plan to make a remaster tool using Pkg, maybe called woofy2, but I'm not sure Pkg
is there yet - it needs to be able to remove built-in packages.. maybe other stuff too..
New syntax for combining packages: pkg combine <pkgname> --sfs|--pet|--deb|--txz|--tgz
(https://gitlab.com/sc0ttj/Pkg/issues/22)
Plugin system:
(https://gitlab.com/sc0ttj/Pkg/issues/13)
If there are any other things people want or need from Pkg, let me know..
If you wanna help out with Pkg, making it more 'woof2' compatible would be nice...
The end goal being that Pkg can help woof build no X puppies.. or be integrated into woof2.. or used as remaster tool..
At some point I plan to make a remaster tool using Pkg, maybe called woofy2, but I'm not sure Pkg
is there yet - it needs to be able to remove built-in packages.. maybe other stuff too..
Last edited by sc0ttman on Sun 02 Dec 2018, 19:06, edited 1 time in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
As per above... Added a new command:
This will split the given package file into separate DEV, DOC, and NLS packages.
The generated packages will be of the same file type as the original - .pet, .sfs, .txz, etc ... (not yet including .deb).
The naming conventions of the new packages will (hopefully) correctly match the package file type (package names will
get either _DEV or -dev, depending on if the package being split is a .sfs, .deb, .txz, .pet, etc)
Example:
1. I created a PET of GIMP with all deps included, using `pkg pkg-combine gimp` ..
2. Then I split the PET into separate DEV, DOC and NLS packages like so:
Another example, using SFS files:
(NOTE: creation of .deb packages not yet implemented.. For now, convert deb packages to PET, then split, if need be)
Code: Select all
pkg split /path/to/package/file
The generated packages will be of the same file type as the original - .pet, .sfs, .txz, etc ... (not yet including .deb).
The naming conventions of the new packages will (hopefully) correctly match the package file type (package names will
get either _DEV or -dev, depending on if the package being split is a .sfs, .deb, .txz, .pet, etc)
Example:
1. I created a PET of GIMP with all deps included, using `pkg pkg-combine gimp` ..
2. Then I split the PET into separate DEV, DOC and NLS packages like so:
Code: Select all
pkg split ./gimp_2.8.18-1+deb9u1-WITHDEPS_stretch.pet
Success: Package split into these new files:
gimp_2.8.18-1+deb9u1-WITHDEPS_stretch.pet
gimp-dev_2.8.18-1+deb9u1-WITHDEPS_stretch.pet
gimp-doc_2.8.18-1+deb9u1-WITHDEPS_stretch.pet
gimp-nls_2.8.18-1+deb9u1-WITHDEPS_stretch.pet
Code: Select all
# pkg split ~/pkg/blender_2.79.b+dfsg0-1-WITHDEPS_stretch_7.5.sfs
Success: Package split into these new files:
blender_2.79.b+dfsg0-1-WITHDEPS_stretch_7.5.sfs
blender_DEV_2.79.b+dfsg0-1-WITHDEPS_stretch_7.5.sfs
blender_DOC_2.79.b+dfsg0-1-WITHDEPS_stretch_7.5.sfs
blender_NLS_2.79.b+dfsg0-1-WITHDEPS_stretch_7.5.sfs
(NOTE: creation of .deb packages not yet implemented.. For now, convert deb packages to PET, then split, if need be)
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
New command: pkg dir2repo (not ready yet)
I've been working on an easy way for users to create and share their own repos..
Feedback welcome!
It's not ready yet... but here's where I got so far..
I created the directory /root/myrepo, and put 2 packages in it.
Then I made some updates to Pkg..
Now Pkg can do the following:
What happens is Pkg goes through each package, builds a standard Puppy repo file,
asks for a repo name and URL, then creates a file called 'install' in the repo dir,
which contains info that Pkg can use to install the repo using `pkg add-repo <repo-url>`.
Note, you can build repos of PET, SFS, txz, deb packages (etc), but you cannot mix and match..
All packages in the repo dir must have the same extension.
EDIT: Here is the usage info (so far):
I've been working on an easy way for users to create and share their own repos..
Feedback welcome!
It's not ready yet... but here's where I got so far..
I created the directory /root/myrepo, and put 2 packages in it.
Then I made some updates to Pkg..
Now Pkg can do the following:
Code: Select all
# pkg dir2repo myrepo
Creating repo from contents of: /root/myrepo
Step 1 of 3: CHOOSE A REPO NAME
(something like 'username-repo', such as 'bob-main' or 'sc0ttman-games')
Type a repo name and hit ENTER: bob-main
Step 2 of 3: ADD THE REPO URL
(the full URL where you will upload your repo file and packages)
Type a repo URL and hit ENTER: http://foo.com/bob-main/
Step 3 of 3: ADD FALLBACK REPOS
(the other repos to fall back to when looking for dependencies)
List fallback repos (separated by a space) and hit ENTER: noarch common32
Success: Repo bob-main created.
You should upload everything in /root/myrepo to:
http://foo.com/bob-main/
You (and anyone else) can then install the repo using:
pkg add-repo http://foo.com/bob-main/
NOTE: You can edit the install and Packages-debian-stretch-bob-main
files in a text editor, before you upload your new repo.
asks for a repo name and URL, then creates a file called 'install' in the repo dir,
which contains info that Pkg can use to install the repo using `pkg add-repo <repo-url>`.
Note, you can build repos of PET, SFS, txz, deb packages (etc), but you cannot mix and match..
All packages in the repo dir must have the same extension.
EDIT: Here is the usage info (so far):
Code: Select all
# pkg usage dir2repo
Usage: pkg dir2repo DIR
Create a Puppy-compatible package repository (repo).
DIR must be a valid directory containing valid packages,
and all packages must have the same file extension.
HOW TO:
Run the command, you will be asked to give a repo name,
repo URL, and optional 'fall back' repos.
The entire contents of the given directory should
then be uploaded to your chosen repo URL.
MORE INFO:
Alongside the packages, a repo file will be generated
in the repo directory, as well as a repo installer file.
You can edit the contents of the following files
before uploading your repo:
Packages-* <-- the repo file
install <-- a repo info file (for installing the repo from URL)
SHARING REPOS:
Repos generated in this way and uploaded online can be
installed by other users simply by running this command:
pkg add-repo <your-repo-URL>
SUPPORTED PACKAGES:
Supported packaged types include PET, SFS, DEB, TXZ.
You can use any supported packages types, but you
cannot mix and match them in a single repo.
Last edited by sc0ttman on Thu 06 Dec 2018, 23:11, edited 2 times in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
I'm just gonna put this out there:
Pkg is really quite good nowadays... And could probably be getting a bit more attention..
It's not perfect, and I still didn't get round to implementing some very useful
commands (like removing builtins) yet... But overall, Pkg is pretty damn good..
The package size in total is only 160kb, the deps are very minimal/standard (busybox, bash,
core-utils, wget, etc), yet Pkg provides a lot of the same features as the "big boys"..
It's easy to maintain and improve on - entirely written in shell script, mostly in one big file
admittedly, but nicely organised into little functions for each task..
It is one of the only package managers with context-sensitive TAB completion, which makes it
super easy to use in the terminal..
But it also has three(!) frontend GUIs - created more as demos that anything else, even if they
mostly work great.. But they can still be made better..
It has a whole bunch of Puppy-specific commands too..
In case people have not realised (the thread is messy), here are the things that Pkg can do already:
* easily find/search for packages to install from a range of repos
* easily add or remove you own repos with a couple of easy commands
* easily install, remove, analyze, convert and combine packages
* easily build/create your own packages (pet, deb, txz, tgz, rpm)
* compile packages from source (supports petbuild, SboPkg - which has lots & lots of build scripts, and the fantastic src2pkg)
* super easy to build custom SFS packages containing all deps needed to run your chosen program
* wrapper script for apt, yum to make copy & paste installation instructions for other distros work in Puppy
* and much more
And stuff Pkg will/can do in future, with additional scripts/modifications:
* easy way to create your own repos and share them, so others can install them with one command! (coming soon)
* could work with EasyOS or FatDog
* provision/setup a Puppy OS remotely (over ssh)
* create installer scripts for various programs much, much more easily
* automated building of custom ISOs (make Pkg work as a remaster tool)
* web frontend for building ISOs (like Slax)
* better support and integrations with amigos src2pkg (<-- this is a very good one to do)
* integration with woof (should remove buildpet, use only petbuild)
* buildpet is great, but it's build scripts are outdated.. they should be updated..
* other stuff
----------------
Also, can anyone please point me to a dir2deb bash function that definitely works in a recent Puppy? ..if it exists..
Pkg is really quite good nowadays... And could probably be getting a bit more attention..
It's not perfect, and I still didn't get round to implementing some very useful
commands (like removing builtins) yet... But overall, Pkg is pretty damn good..
The package size in total is only 160kb, the deps are very minimal/standard (busybox, bash,
core-utils, wget, etc), yet Pkg provides a lot of the same features as the "big boys"..
It's easy to maintain and improve on - entirely written in shell script, mostly in one big file
admittedly, but nicely organised into little functions for each task..
It is one of the only package managers with context-sensitive TAB completion, which makes it
super easy to use in the terminal..
But it also has three(!) frontend GUIs - created more as demos that anything else, even if they
mostly work great.. But they can still be made better..
It has a whole bunch of Puppy-specific commands too..
In case people have not realised (the thread is messy), here are the things that Pkg can do already:
* easily find/search for packages to install from a range of repos
* easily add or remove you own repos with a couple of easy commands
* easily install, remove, analyze, convert and combine packages
* easily build/create your own packages (pet, deb, txz, tgz, rpm)
* compile packages from source (supports petbuild, SboPkg - which has lots & lots of build scripts, and the fantastic src2pkg)
* super easy to build custom SFS packages containing all deps needed to run your chosen program
* wrapper script for apt, yum to make copy & paste installation instructions for other distros work in Puppy
* and much more
And stuff Pkg will/can do in future, with additional scripts/modifications:
* easy way to create your own repos and share them, so others can install them with one command! (coming soon)
* could work with EasyOS or FatDog
* provision/setup a Puppy OS remotely (over ssh)
* create installer scripts for various programs much, much more easily
* automated building of custom ISOs (make Pkg work as a remaster tool)
* web frontend for building ISOs (like Slax)
* better support and integrations with amigos src2pkg (<-- this is a very good one to do)
* integration with woof (should remove buildpet, use only petbuild)
* buildpet is great, but it's build scripts are outdated.. they should be updated..
* other stuff
----------------
Also, can anyone please point me to a dir2deb bash function that definitely works in a recent Puppy? ..if it exists..
Last edited by sc0ttman on Sat 08 Dec 2018, 11:25, edited 1 time in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Re: Pkg - CLI package manager
It may have some learning curve but I did the above and thensc0ttman wrote:Download latest: https://gitlab.com/sc0ttj/Pkg/-/archive ... ter.tar.gz
(extract then run 'installer.sh).
Code: Select all
# pkg repo-update
Updating repositories.. Please wait.
Repo files updated:
Packages-slackware-14.2-official
Packages-slackware-14.2-salix
Packages-slackware-14.2-extra
Packages-slackware-14.2_updates-official
# pkg repo-list
noarch
#ls .packages/Packages-*
.packages/Packages-puppy-common32-official
.packages/Packages-puppy-noarch-official
.packages/Packages-puppy-slacko14.2-official
.packages/Packages-slackware-14.2-extra
.packages/Packages-slackware-14.2-official
.packages/Packages-slackware-14.2-salix
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Pkg is really quite good nowadays... And could probably be getting a bit more attention..
Please do not think that people are not looking at this and not following your progress in development!!!!!!
We are following your progress in development!
With something that can do all that you post about it.
It takes some time to check it all.
Anything that can deal with program packages needs to be used with some caution.
We all understand that program packaging is always a problem getting it correct for Puppy.
Even more so when you try to use stuff from non-Puppy repositories.
Pkg is looking like a very good feature rich program.
Keep up the work on this!
We are watching what you are doing!!!!!!!!
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
I totally agree.bigpup wrote:Pkg is really quite good nowadays... And could probably be getting a bit more attention..
Please do not think that people are not looking at this and not following your progress in development!!!!!!
We are following your progress in development!
...
Pkg is looking like a very good feature rich program.
Keep up the work on this!
We are watching what you are doing!!!!!!!!
I was a fan from the first time I came across this, at the beginning, and it's been on my short watch list ever since.
It's amazing at what pace it develops and what it aims for.
I sometimes wonder if it will take the place of woof-CE (I'm sure not.)
To me it looks obvious it will eventually take the place of PPM. As I understand it is compatible with it, which is a big advantage for Puppy.
Great work sc0ttman!
I intend to try and test it more in future and report, but it is true it has some learning curve.
Re: Pkg - CLI package manager
It may be that you needed to runmavrothal wrote:It may have some learning curve but I did the above and thensc0ttman wrote:Download latest: https://gitlab.com/sc0ttj/Pkg/-/archive ... ter.tar.gz
(extract then run 'installer.sh).Is this the expected behavior? (I would think that existing repos would be used or at least considered)Code: Select all
# pkg repo-update Updating repositories.. Please wait. Repo files updated: Packages-slackware-14.2-official Packages-slackware-14.2-salix Packages-slackware-14.2-extra Packages-slackware-14.2_updates-official # pkg repo-list noarch #ls .packages/Packages-* .packages/Packages-puppy-common32-official .packages/Packages-puppy-noarch-official .packages/Packages-puppy-slacko14.2-official .packages/Packages-slackware-14.2-extra .packages/Packages-slackware-14.2-official .packages/Packages-slackware-14.2-salix
pkg update-sources
pkg repo-update
pkg repo-list
IIRC, the first one should run itself on first load, but maybe it's not working..
Or maybe I need to boot a slack pup and fix some stuff..
(You can see all repos (currently) supported in the ~/.pkg/sources-all file)
------------
I should say I hope my previous post didn't sound like a rant or complaint - more that I
realise the thread is a lot of just me talking to myself, and probably not as clear to
understand the point of it all for others as it is to me..
.. but Pkg is a bit more involved and in-depth than many other forum based user contributed scripts/programs...
So I glad I'm not the only one using it..
............
As for Pkg having a steep learning curve... True - I proposed to fix this a while back by doing the following:
* create a proper `pkg init` command, run by installer (or user later) that does all the required setup stuff
* strip out some less often used commands from help output (-h) but leave them in full help output (-H)
* advertise and improve Gpkgdialog, Pkgdialog and Xpkgdialog a bit more
...Also, if this helps, here is a "quick help" summary that does 90% of what people might need:
SETUP
pkg update-sources # update supported repo list
pkg repo-update # download latest repo files and use them
CHOOSING REPOS
pkg repo-list # list all available repos by name
pkg repo <repo-name> # switch to chosen repo
SEARCHING
pkg search <search-term(s)> # search repo for any matches
pkg names <pkg-name(s)> # list matching packages by name
INSTALLING & REMOVING PACKAGES
pkg add <pkg-name(s)> # download and install a package and its deps
pkg rm <pkg-names(s)> # uninstall a package and any left-over (unused) deps
...plus the other stuff (run `pkg help` to see all commands)
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]