On Wed, Jun 11, 2008 at 2:25 AM, Cilyan Olowen <[EMAIL PROTECTED]> wrote:
> Is it really such a hard work to parse PKGBUILD and simulate a bash
> behaviour only on variables preceding the build() function ?
> The parser needs to be able to :
> - affect and replace variables
> - support arrays
> - s
Is it really such a hard work to parse PKGBUILD and simulate a bash
behaviour only on variables preceding the build() function ?
The parser needs to be able to :
- affect and replace variables
- support arrays
- support the simple ${x//find/replace} syntax
- what else ?
If this can be tedious with
On Tue, 10 Jun 2008 15:16:29 +0800
"Callan Barrett" <[EMAIL PROTECTED]> wrote:
> Note to self: restricted mode is apparently not as restricted as it
> sounds, need to look into that and probably how namcap deals with it.
>
> Possibly a chroot?
>
> Also I'm assuming everyone is fine and dandy wit
On Tue, Jun 10, 2008 at 1:08 PM, Simo Leone <[EMAIL PROTECTED]> wrote:
> On Sun, Jun 08, 2008 at 09:24:36PM +0800, Callan Barrett wrote:
>> Gonna have to resubmit packages before results are correct.
>>
> An SQL query or simple php script can also do this. You might want to
> write one and send it
On Sun, Jun 8, 2008 at 7:19 PM, Callan Barrett <[EMAIL PROTECTED]> wrote:
> Ok this is a test to get a bash script to parse pkgbuilds rather than
> the current crazy way it's done now.
>
> The pkgbuild is sent through a bash script (thanks Xilon) and the vars
> are output so the result can be evalu
