yeah. worse than that, i made a respin of antix 16.2 that has petget.

though that wasnt a specific goal. the goal was to find out how much of mkfigos i would have to modify to make it respin antix (full) instead.

the changes are here: (then an explanation)


* NOTE: I DIDNT UPLOAD THE FILE YET.

when i tried to post this, i got a real nastygram from cloudflare. GUYS! its a 52k plaintext file. what do... fine, i will upload it somewhere else and link to it here.


* the goal of this script was to find out how much of mkfigos i would have to modify to make it respin antix.
* this is a fully automated script with no user input. the necessary changes made to it are listed in this post.
* it successfully made a new iso for antix with several changes-- including adding fig, some utilities written in fig, and also petget from puppy linux.
* petget works-- i installed audacious in this"respin" of antix.
* fig os normally mixes librepup with refracta (latest version: 8.3)
* one of the really nice things about the previous version of mkfigos was that it fixed dirty cow before refracta did.


the way i started remixing distros was by trying to sort out the differences between all the many puppy versions (even over time, such as very old versions based on the 2.x kernel.)

i found out no one else was interested in this deep analysis of puppy distros (a little bit surprising, and yet not a lot.)

i created a utility called"distdiff" which instead of producing a table of things found in many isos, would compare two isos along with the contents of their squashfs files.

then i watched people struggle to use the official puppy build script. i wanted to find out if there was a way to UPDATE PUPPY by mixing its files with debians. there were two modes; the script took librepup and refracta and made it boot into either:

* puppy mode: puppy with some parts updated from refracta
* refracta mode: refracta with some parts imported from puppy (like petget)

it was a race to find out what was easier: update puppy from refracta binaries? or TRULY puppify refracta. refractahrpup could potentially do both.


how did it become fig os?

* no interest in puppifying refracta, even if i was doing all the work
* refracta dev (who ive met in person) thought the name"refractahrpup" might confuse some
* a close friend from the puppy community thought it was better without"puppy" in the name
* ...he made a fig boot screen for me, too

i updated puppy mode as much as i could-- with TONS of fresh binaries from refracta. it got to where i had to do surgery on initrd; thats where i stopped. with no audience i got as far with puppy mode as i wanted; and dropped the feature.

when i say"dropped the feature" all i have to do to pick it back up is add some code back. from an older version.

now ive modified mkfigos to remix antix instead. it doesnt make all the proper edits to antix that it makes to refracta, but i believe it can.

it makes the new iso-- it boots into the default graphical desktop (with shells and roxterm) and worst of all! it has a working installation of petget.

i will even attach the source to this bizarre public domain respin code. i made the minimum modifications to get a working, graphical, bootable puppy/antix hybrid. yes! now thats a thing... dont worry, i have no reason to pursue that at this time.

when i tried to post this, i got a real nastygram from cloudflare. GUYS! its a 52k plaintext file

idunno how cloudflare fits in the mix, but...
to upload plaintext forum attachments, I've been forced to append .zip to filename (just rename, no need to actually compress)

From my perspective, use of petget is worrisome, in the same vein as using/trusting content blindly installed from PPAs (or wget'ted from clowdz).
I do keep an eye on puppyland tech, though

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://barryk.org/easy/how-easy-works.htm"
linktext was:"http://barryk.org/easy/how-easy-works.htm"
====================================
(go ahead, try to read, and digest, that in one sitting -- I couldn't)
-=-

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://distro.ibiblio.org/fatdog/web/faqs/uml.html"
linktext was:"http://distro.ibiblio.org/fatdog/web/faqs/uml.html"
====================================
(keywords: virtenv, isolation, lxc containers)

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.lightofdawn.org/blog/?viewDetailed=00028"
linktext was:"http://www.lightofdawn.org/blog/?viewDetailed=00028"
====================================


An"adrive" [...]"zdrive" mechanism doesn't jibe well with a dpkg -managed system, but I'd like to work out a way to conditionally side-load
infrequently needed"stuff" during liveboot. (Immediate example is LibreOffice.) Shuffling appimage loaders into, and out of,
a watched directory on the liveUSB should be possible... but I'd prefer an ability to choose"create a diversion" when installing debian packages,
so that LO (and its myriad"personal bloatation devices") could be relegated to a separately-loadable"layer".

a user would be generally unwise to mix apt with puppy packages on an installed system. sooner or later its going to do-- something.

for a livecd i think its fine, petget happens to be my favourite part of puppy but more importantly, there are many packages for puppy that you can now run-- and when debian drops them in newer versions, theyre still available. i think avidemux is one example.

not that its ever a great idea to mix repos, let alone package systems. and yet every once in a while, an exception can come up. when i added petget, it was a demo.

to me, if youre going to mix puppy with anything, you cant have puppy without petget. you probably need a lot of other things, too-- but petget is essential, because people want to be able to use their packages (and a lot the puppy packages are unique, even if compatibility is never guaranteed.)

if i were going to maintain (rather than just demo) petget or offer it as a serious idea for including, it would need a lot of cleanup. barrys stuff is usually very tightly coupled, difficult to separate into standalone components, and no one seems to have any interest in doing that. i would probably modify petget so that it cant clobber any existing files-- though that would make upgrades difficult or impossible-- petget is designed to clobber. having it check apt to avoid stepping on its toes would be a feat, but probably too much work for something no one would actually use.

Hi guys,

This is my first post, and I've not yet used antiX, although I read some reviews and it looks great..
I particularly like your installer GUI, is it gtkdialog? Is there source available for it?

...Anyway, about this thread: I have made a command line package manager for Puppy Linux.

Currently found here, in a discussion I'm trying to start about (lack of) Puppy CLI apps:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://murga-linux.com/puppy/viewtopic.php?p=967038#967038"
linktext was:"http://murga-linux.com/puppy/viewtopic. ... 038#967038"
====================================


It is called Pkg-1.9.0alpha ... It uses some Puppy repo stuff in ~/.packages ...
I wouldn't even think about trying to port it to AntiX until 1.9.1alpha is released..

I post about it here because it may be an easier (or not!) way of getting Puppy repos and PETs available in AntiX,
without the need to bring it in PetGet and all its config files, etc..

It is currently very, very early alpha stages (only works well on Slacko-6.9.x, which are the latest Slackware based pups)..
But soon it should work work in all recent Puppy Linux builds, and most Woof-built pups (4.3 and later)..

Anyway, if any mad people on this forum WANT to get Puppy Linux PETs in to AntiX,
this CLI package manager may be something to try... Just FYI.

Cheers,
Good luck on the great looking distro and its excellent custom tools!

Scott

Hi, Scott. The antiX installer GUI is written in C++ and has a QT frontend. Its source code is posted here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux/antiX-installer"
linktext was:"https://github.com/antiX-Linux/antiX-installer"
====================================


Source code for most of the antix in-house tools are posted to separate github repos, under antiX-Linux project

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux"
linktext was:"https://github.com/antiX-Linux"
====================================


antiX ships with gtkdialog pre-installed. IIRC, it is a slightly higher version (v0.8.3) than most puppy variants use. Its tarball is available here:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antixlinux.com/jessie/pool/main/g/gtkdialog/"
linktext was:"http://antixlinux.com/jessie/pool/main/g/gtkdialog/"
====================================

Although the newer version introduces some new functionality and fixes a couple bugs, some quirks arise in puppy applications expecting the older version. An example, from (my) recent memory:
SFR's Yahtzeeeee game
I had to make several modifications to get it to run under antiX, period, and never managed to get it to run flawlessly (roll2, roll3 actions didn't respond).

Because antiX includes JWM and rox, it may provide a comfortable transition to puppy emigrants.
Hey {click} I just realized: antiX even includes a
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux/advert-block-antix"
linktext was:"advert-block-antix "
====================================
util derived from your
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://murga-linux.com/puppy/viewtopic.php?t=59290"
linktext was:"Advert-Blocker"
====================================


Please do at least test-drive antiX. Aligned with your
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://murga-linux.com/puppy/viewtopic.php?t=111468"
linktext was:"Better command line tools, and pkg manager suggestions,"
====================================

within the antiX17beta you'll find
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux/console-grid-gui"
linktext was:"console-grid-gui"
====================================

hi sc0tt, the only real point of having petget in fig os (originally refractahrpup) was to show how you could take barrys stuff and merge it with another distro.

i dont think theres really anyone on earth who wants to use petget outside of puppy, but if they do its not impossible.

the point of showing petget in antix was mainly to demonstrate that mkfigos works on antix-- i normally use it with refracta. just to reiterate, i have scripts that used to merge puppy (librepup, based on puppy tahr) with debian-based distros like refracta and antix. dont get me wrong, being able to install .pet packages that easily has actually helped one or two times. have fun.

sc0ttman wrote:...Anyway, about this thread: I have made a command line package manager for Puppy Linux.

We added a command-line Debian package manager to antiX-17.    It is written in Bash and makes use of a fairly powerful library that is available here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/BitJam/cli-shell-utils"
linktext was:" cli-shell-utils"
====================================
.   IIRC, four of our programs use this library now: cli-aptiX, live-usb-maker, dd-live-usb, and live-kernel-updater.   The UI elements are all menus that are navigated with the arrow keys, etc.   I made a screenshot to show you the UI but I was not able to attach it.

Thanks for the info guys.

I will install antiX when I have a bit more time, might need to buy some USBs before I can play around with some new stuff..

Cheers for the links to your GitHub stuff, I will have a good look around, already seen some nice stuff!

As for many people not wanting to use PetGet, that includes some Puppy users too I think! :)

Cheers,
Scott.

at least its not called pupget anymore (or more importantly, theyre not called"pups")

mcafee uses"pup" as an abbreviation for"potentially unwanted programs." i wouldnt be surprised if that went into barrys reasons for the change.