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

Code:

pkg <command> ./path/to/local/file

and

Code:

pkg <command> ../path/to/local/file

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

Code:

pkg repo-list [TAB]

you will get a list of all repos auto completed (not local files and dirs)..

And if you do

Code:

pkg uninstall [TAB]

you will get a list of all installed packages (not local files or dirs)

And if you do

Code:

pkg add gimp[TAB]

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._________________Akita Linux, VLC-GTK, Pup Search, Pup File SearchLast edited by sc0ttman on Sun 18 Nov 2018, 12:15; edited 1 time in total

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.._________________Akita Linux, VLC-GTK, Pup Search, Pup File SearchLast edited by sc0ttman on Sun 02 Dec 2018, 15:06; edited 1 time in total

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:

NOTE: You can edit the install and Packages-debian-stretch-bob-main
files in a text editor, before you upload your new repo.

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):

Code:

# 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:

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.._________________Akita Linux, VLC-GTK, Pup Search, Pup File SearchLast edited by sc0ttman on Sat 08 Dec 2018, 07:25; edited 1 time in total

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) http://www.murga-linux.com/puppy/viewtopic.php?t=107601

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 totally agree.
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.

Is this the expected behavior? (I would think that existing repos would be used or at least considered)

It may be that you needed to run

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:

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum