[V2] tag-rule does not work with version information in directory names

From: Juergen Hunold (hunold_at_[hidden])
Date: 2005-04-05 12:52:32

Hi !

The current "tag" rule mechanism does not work with directories which 
encode version information in their name, e.g boost-1.33.0

Please find a test case attached.
tag-test has two identical project, one name tag-works and one name 
tag-1.0.0. Both contain a copy of the hello example from current CVS 
just in order to provide some work for bjam.
tag-works works as expected and builds the hello example in bin.v2.

When running bjam --v2 in tag-1.0.0, I get

bjam Version 2
/home/hunold/packages/boost/tools/build/v2/kernel/modules.jam:66: in 
modules.call-in
rule Jamfile</home/hunold/src/bjam/tag-test/tag-1.0.0>.tag unknown in 
module Jamfile</home/hunold/src/bjam/tag-test/tag-1.
/home/hunold/packages/boost/tools/build/v2/util/indirect.jam:82: in 
indirect.call

Please find full output attached in out.zip.
Please note that some something inside Boost.Build strips everything 
after the first dot from tag-1.0.0 when trying to find the matching 
rule...
One even easier test is to rename the CVS checkout (_no_ symlink ;-) to 
read boost-1.33.0 and then do (cd status; bjam --v2), this will fail 
also.

I'd call this a show-stopper ;-((

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover 
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] ! www.ive.uni-hannover.de
 --Boundary-00=_hBtUCwZWccivlZp Content-Type: application/x-tbz;
name="tag-test.tar.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="tag-test.tar.bz2"
[Attachment content not displayed.] --Boundary-00=_hBtUCwZWccivlZp Content-Type: application/x-zip;
name="out.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="out.zip"
[Attachment content not displayed.] --Boundary-00=_hBtUCwZWccivlZp--