[gobolinux-devel] Idea for Compile

Jonas Karlsson jonka750 at student.liu.se
Fri Aug 11 11:26:39 GMT 2006


On Fri, 11 Aug 2006 04:51:06 +0200, Lucas C. Villa Real  
<lucasvr at gobolinux.org> wrote:

> On 8/10/06, Jonas Karlsson <jonka750 at student.liu.se> wrote:
>> On Thu, 10 Aug 2006 23:34:22 +0200, Lucas C. Villa Real
>
>> >> fibosandbox_options=(
>> >>     "--add-alloved=${goboModules}/Current/misc"
>> >> }
>> >>
>> >> unionsandbox_options=(
>> >>     "unmanaged_files=(${goboModules}/Current/misc)"
>> >> )
>> >
>> When I think about it, I don't like it either. But I do think there has  
>> to
>> be something to take care of the transition between fibosandbox and
>> unionsandbox. Perhaps the --add-allowed option for fibosandbox is  
>> handled
>> as an unmanaged directory in unionsandbox?
>
> Looking better on the subject, isn't it better to just let fibosandbox
> deal with unmanaged_files instead? That way we don't need to enlarge
> the Compile API, while keeping the syntax simple. Something like
> (needs to make proper handling of arrays):
>
> if [ "$unionsandbox" ]
> then # keep using $unmanaged_files like it's doing now
> else sandbox_options="--add-allowed=$unmanaged_files"
> fi
>
You can already use "--add-allowed" as an option to the sandbox_options  
array, so using that isn't an enlargement of the API. But maybe we should  
allow both ways around, as there already are recipes with --add-allowed,  
but labelling the sandbox_options deprecated?

-- 
/Jonas

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/


More information about the gobolinux-devel mailing list