On 20/06/2008, at 4:22 PM, Simo Leone wrote:
On Fri, Jun 20, 2008 at 12:54:29AM +0800, Callan Barrett wrote:
Here's another iteration of this patch, I'm still looking for as much
input as possible but this is basically what I would push to testing
at this point. The script now outputs in a dif
On Fri, Jun 20, 2008 at 12:54:29AM +0800, Callan Barrett wrote:
> Here's another iteration of this patch, I'm still looking for as much
> input as possible but this is basically what I would push to testing
> at this point. The script now outputs in a different format to be
> parsed and there is so
On Fri, Jun 20, 2008 at 12:54:29AM +0800, Callan Barrett wrote:
> Here's another iteration of this patch, I'm still looking for as much
> input as possible but this is basically what I would push to testing
> at this point. The script now outputs in a different format to be
> parsed and there is so
Here's another iteration of this patch, I'm still looking for as much
input as possible but this is basically what I would push to testing
at this point. The script now outputs in a different format to be
parsed and there is some cleanup done in pkgsubmit.php to get it
working more cleanly with the
On Fri, Jun 13, 2008 at 2:17 AM, Sebastian Nowicki <[EMAIL PROTECTED]> wrote:
>
> On 10/06/2008, at 12:16 AM, Callan Barrett 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.
>
> What do you mean
On 10/06/2008, at 12:16 AM, Callan Barrett wrote:
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
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 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
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 evaluated by PHP, this way nothing can
get missed and there are no bugs with what's pars
11 matches
Mail list logo
