Hi,
OK, You are right. I will do that. But what do you think about dropping
the spark version in soccer3d repository immediately after that? Then,
simspark changes will be followed by the corresponding changes in
soccer3d. If not, I think the current situation will last for ever!
I think that I will need your help from time to time, so I want to say
thanks for your patience! :)
Good luck,
Hedayat
/*Markus Rollmann <rol...@un...>*/ wrote on 02/18/2008
01:44:06 PM:
> Hi,
>
> Hedayat Vatankhah wrote:
> [...]
>
>> But about selecting a repository, what about removing the spark core
>> libraries (oxygen, kerosin, ...) and other things which are currently in
>> simspark from soccer3d repository? For now, we could just split two
>> repositories so that the soccer3d code requires simspark installed on
>> the system.
>>
>
> You want to use the libraries from the simspark repository tpgether with
> the simulation from the soccer3d repository, right?
>
> I think thats not practical as the two spark version have various
> differences that does not allow a for a simple replacement (see my 2nd
> mail for a list of differences)
>
> Therefore keeping a known working version (the soccer3d repo) and
> gradually picking changes from the simspark repo is my preferred way.
>
>
>> To make it simpler for users, we could then release them as
>> one package, so that they will not notice the change. (Also, I will
>> release RPM/SRPM packages for them). At least, it is more fun I think!
>>
> [...]
>
> The idea to release rpm or debian packages is good I think and would
> ease the installation process for the user.
>
> cheers,
> Markus
>
>
|
