Porteus-AUR: Building Porteus modules w/ Arch build scripts!

[francois]

Hello, amigo. You have all my respect. However, according to spbuilder, they would have find some way to cirumvent the problem. Have you been working with spbuilder? If its the case forgive my intervention.

spbuilder for slackware: generates a new, completely separate, minimal Slackware environment in which the package's build script is executed.
http://www.vislab.uq.edu.au/howto/spbui ... ilder.html

[brokenman]

A quote from their page:

Issues
The very basic ability to work with standard Slackware® or SBo build scripts is of limited value at the moment since they have no (or not enough) fields to fully describe prerequisite packages for building. However quite minor changes to SBo packages can allow them to fully utilize spbuilder's capabilities.

The quite minor changes they speak of requires editing every .info file in the repository that is not written correctly. In short, they are saying that it is an automated build system, but it won't resolve build time dependencies.

The basic problem is that people don't follow a standard. If every SBo had a correctly written .info file then this would work but the fact is that they don't. Because of this any reliable dependency resolution is almost impossible. I would love (probably more than most people) for SBo to be fail proof and build everything but I don't think this is realistic at the moment.

[francois]

Is it possible to adapt porteus-aur to porteus 3.0? usm is really more efficient than ppm was.

[francois]

Forget about it. Finally, I just realized that no matter the porteus version. It will work.
Great.

[ViktorNova]

Glad you are finding it useful!

I have admittedly not used this on Porteus in awhile (someone made a Porteus-ized verison of Debian and I have been kinda hooked on that), although this does work on other OSs besides Porteus! When it is a little more put together I plan to call it "Architect"

The arch packages this is using (expac, pacman, etc) were ones I just directly converted from Arch binary packages, so if at any point they stop working (if I haven't gotten around to fixing it yet) you can just convert the same packages from Arch current or build them yourself from source. This method isn't actually anything I wrote, just a specific way of using tools other people made for Arch!

[francois]

Some automation of dependencies resolution would be really great.

Do you have that link to porteus-deb?

Ok, I have it, see:
http://www.murga-linux.com/puppy/viewtopic.php?t=90660