s243a wrote:sc0ttman wrote:
Of course, I first and foremost intend to get Pkg working in official Puppies ...
Your devuan acsii version is an 'edge case', for now...
Not sure if the following is an "edge case issue" or a woof-CE issue
If you are not running a standard Puppy (which you are not), then for Pkg it's 100%
an "edge case" - because Pkg is designed (mainly) for standard Puppy Linux releases.
I have no idea if your custom OS (half Puppy, half something else) has everything setup
correctly... I don't even know if it was built with Woof... Hence,
your OS is the "edge-case"
as far as Pkg development is concerned.
Anyway, I tried to work out if it's a Pkg issue....
I know that the package manager...
Which one?? Pkg? PPM? PPM 3.0?
..writes to the actual save layer but in my case
the save layer is:
.....
Edit: After further examination this might be an issue with mistfire's package manager.
I search for pup_ro1 returns nothing that seems relevant in the gitlab branch for pkg.
Then I think you should probably post it at the PPM 3.0 thread, or even better work out if it's
actually a Woof-CE issue before posting at either... I guess..?
I did notice though that pup_r01 is used in sfs_loadr.
Code: Select all
6) SAVE_LAYER='/pup_rw'; PUP_HOME='/pup_rw'; PUPSAVE='sda1,ext2,/';;
12) SAVE_LAYER='/pup_rw'; PUP_HOME='/mnt/dev_save';;
13) SAVE_LAYER='/pup_ro1'; PUP_HOME='/mnt/dev_save';;
77) SAVE_LAYER='/pup_ro1'; PUP_HOME=''; PUPSAVE='sr0,iso9660,/2011-01-27-20-26';;
/usr/sbin/sfs_loadr#L1697
....
I think that PUP_HOME should either be /mnt/home or /initrd/mnt/dev_save/
**note that /mnt/home is a symlink pointing to /initrd/mnt/dev_save
Yep.. That is what I have on my system (Stretch RC something..) and most Pups I'd imagine..
But it depends on the install method/type... Sorry but I can't reproduce those issues..
...More generally ...
I think maybe you're posting "too soon", if you don't mind me saying so...
The first long series of posts you posted to the Pkg thread turned out to be your /etc/DISTRO_SPECS
not being setup correctly, which wouldn't have happened in a standard Puppy...
And sorry, but I also don't want this thread mixed up with mistfires PPM 3.0 (which literally runs
against to the goals of this project).. Pkg is not designed to support PPM 3.0 (unless it becomes
Puppys official/main PPM).. even then, Pkg aims to become independent of any PPM..
...
I think you should probably test Pkg on a standard Puppy to compare to your OS before posting any
issues here in order to make sure the issues are with Pkg and not your custom OS..
It's nice that you're sharing all your devuan-ascii Woof-next/[tazPup?/TinyCore?] endeavors on the forum,
but it should probably be in it's own thread, and anything posted here should relate to Pkg on a
standard Puppy release (that is, a Puppy built in the usual way, with a standard Woof-CE setup)..
.. or at least until you are 100% sure the Pkg problem exists in a standard Puppy too...
And FYI, people:
There are already a whole list of Issues for Pkg (see first post), it would be nice if people try to tackle those,
cos some are dead simple - add a dir2deb function, add a --list-builtins command, and so on...
Any Pkg Issues tackles should be added a Merge Requests (Pull Requests/PRs) on the GitLab page..