13 Jan
2014
13 Jan
'14
1:24 p.m.
It may sound like two dumb or unrelated ideas, but I figure they would become relevant to the discussion at one point anyway. So, let's look at the question we're avoiding all the time: What is the problem with PKGBUILDs? That it's not limited to a subset of sh? There seem to be regularly efforts appearing and disappearing to clean that mess up on the initial side of the problem, which could render this .AURINFO / .SRCINFO ballet unnecessary. How about creating a parseable and functionally equivalent "PKGBUILD.gen" from PKGBUILD? cheers! mar77i