Re: RFC: Fixing project-ids and use-project

From: TEMPLIE Cédric (cedric.templie_at_[hidden])
Date: 2005-01-18 04:00:00

David Abrahams wrote:
>>
>>Use case 1 ("external project"). I want to use C++ Boost. I'd expect
>>to write
>>
>> use-project /home/ghost/boost/cvs ;
>>
>>and then have convenient ids for all boost libraries.
> 
> 
> That's good, but for what it's worth, I don't think it would be an
> unreasonable burden to ask users to specify the "local" project ID
> (the one that can be used in the specifying project and all
> subprojects) in use-project:
> 
> use-project boost : /home/ghost/boost/cvs ;
>

I agree, in fact it is interesting to be able to set its own name for a 
project.

> 
>>Use case 2 ("internal project"). I want to use project id to refer to some 
>>directory inside my project, to protect against directory reorganisation.
> 
> 
> use-project internal-project-id : some/relative/path ;
> 
> 
>>Use case 3 ("aliases"). I want to use two different project id for the same 
>>project. Or, I want two use two different project ids for two different 
>>project, even if they define the same project id.
> 
> 
> use-project project-id-1 : some/relative/path ;
> use-project project-id-2 : some/relative/path ;
>

That is what I need :)

> 
>>Problem 3. The project ids are all "global" -- they share the same namespace. 
>>It means that something like
>>
>> use-project boost-cvs : /home/ghost/boost/cvs ;
>> use-project boost : /home/ghost/boost/release ;
>>
>>is not possible, since Jamfiles in both location will define the same global 
>>project id "boost".
>>
>>If we want to solve the third problem, it means that we need "local" project 
>>ids. So, "/boost//" can mean different things in different Jamfiles.
> 
> 
> Yes.
>

agree

> 
>>But then we have:
>>Question 1. Should there be any meaning of "relative" project ids. Now, all 
>>ids start with "/". If ids can be local, it's reasonable to drop "/" from 
>>them. But that would require updating of all Jamfiles, which is not 
>>desirable.
> 
> 
> I don't understand. The fact that dropping the leading "/" is allowed
> doesn't make it required. Users can choose whether to switch to
> relative IDs or not.
>

It make sence.

> 
>>Problem 4. Subprojects. After 
...
>>

I do not understand the problem 4... Maybe with some example I will 
understand and can give my opinion...

Thx again for your work.

TEMPLIE Cédric