[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Last problem with cameleon



Sven Luther <luther@dpt-info.u-strasbg.fr> writes:

> On Thu, Jan 02, 2003 at 06:16:29PM +0100, Jérôme Marant wrote:
>> Hello,
>> 
>>   First of all, Happy New Year!
>> 
>>   I'm sorry I'm very late in updating Cameleon with respect
>>   to the ocaml policy but I encountered a final problem:
>>   2 of the cameleon packages provide a small library that
>>   it is not worth shipping outside of the package.
>
> I have the same problem with advi also.
>
> What package are they with ?

mlchat and ocaml-report.

> One solution would be to provide them in a cameleon-common or soemthing
> such, and still keep the nativecode/bytecode split.

I don't like this.

> Another solution would be to do as i plan to do for advi, that is modify
> the policy so that such packages can be done in native code and in
> custom built bytecode. (or not custom built bytecode, but in the advi
> case at least i didn't easily manage to make them non-custom built).

I like this. :-)

>>   Hence, it is not possible for me to make them Arch:all.
>>   I have to solutions:
>>   - shipping a native package and a byte package ; this
>>   solves the problem but the native package it not
>>   necesssary at all
>>   - making an exception for such packages because their
>>   are like libraries ship with some binaries, i.e.
>>   leaving them Arch: any.
>
> Or modify the policy to accomodate them ? :)))

I like this :-)

>>   Any opinion?
>
> Hope this helps some.

A lot. Thanks.

Cheers,

-- 
Jérôme Marant

http://marant.org



Reply to: