I am trying, but this is not a simple thing. Subsequent to Woof being released Arch has decided to change their repositories over to xz compression. The base Woof scripts only deal with PET and tar.gz files. I have got the scripts revised to deal with xz, however there are other items that will also need to be addressed.

One of the items is discussed on Barry's blog, and deals with version numbers for some packages containing a variable field. He mentions Amarok specifically and basically put a quick fix into Woof to remove any such package. I have also found the variable substitution in three other package names, and unlike Amarok these we just can't ignore. One other item I have run across I am still trying to figure out if I need to fix or not. I believe Woof assumes that packages must contain the string 'i686'. This is not always the case as a select few Arch packages contain the string 'any' indicating they can be used for both i686 and x86_64 builds. I am still working on translating the Woof scripts so I am not entirely sure on this. I'm a C++ guy and the arguments supplied to grep in the scripts look to me like cartoon characters trying to swear.

I have made several attempts a building an Arch Puppy, but I was never able to get Xorg to give me a desktop. I have now taken the Quirky 100 configuration file and am using that as a base for my next attempt, basically discarding the Arch configuration file supplied in Woof. If I have any success I'll post it here, but it is likely to be a bit.

Subsequent to Woof being released Arch has decided to change their repositories over to xz compression. The base Woof scripts only deal with PET and tar.gz files. I have got the scripts revised to deal with xz, however there are other items that will also need to be addressed.

I had seen Barry's comments about getting XZ working for Slackware. I have not checked the Slackware packages, but Arch is (was?) in the process of converting from GZ to XZ so you need the scrips to check for both and uncompress as appropriate. I think I had gotten past that issue with the Arch build, and the scripts were actually fairly easy to revise. Incidentally, if anybody wants to see what I had managed to code I'd be happy to send my revisions to you.

My problem now is time. We are currently in the brief period of the year where it is not a million degrees below zero outside, so I am afraid I am not currently spending lots of hours indoors sitting at the computer. All too soon and I'll be back on it however.

On my last attempt I actually managed to boot up an Arch Puppy. Unfortunately I had to use VESA and it came up with a blank desktop, however XSoldier worked. Hardly a usable system, but believe me, it was progress.

Big_Bass, I will definitely check out your link to see if there is something I can use.

with an added ability to build Arch Linux packages in a Slackware format

Could that approach be a way forward? Not that Puppy is slackware based at all but Spup do use such resources so some Devs already are familiar with it._________________I use Google Search on Puppy Forum
not an ideal solution though

The forum announcement of RC2 says, "We have added the ability to build archlinux packages in slackware format in both the abs and aur with a special script unique to VectorLinux." This script takes an Arch PKGBUILD, like this one for libglade, and builds a package to Slackware's package specs rather than Arch's.

Lots of projects use build scripts. Salix OS uses slkbuild, inspired by the Arch Build System and SlackBuilds, to create Slackware packages, and Slitaz uses its own system to build from scripts. Iguleder has something called Puppy Ports in the same vein. I personally used slkbuild to build packages to use in Spup.

So only archiso booted and archbang failed to find what it needed and failed to go anywhere,

If arch is that good then it would allow me to do a frugal install on NTFS.

or else them want to play as hard as possible for the noob to only get those that reformat their hdd.

Maybe I could get it to boot from USB? I don't have CDROM on the Acer D250.

Arch has existed for many years now. Why do them still fail to have an easy way to boot with frugal install on NTFS? May I guess them look down on such noob ways of doing things? Why else be that hard to get._________________I use Google Search on Puppy Forum
not an ideal solution though

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