problems using libtoolize with cloned repo

Stephen torri <[email protected]>
Newsgroups gmane.comp.version-control.bitkeeper.user
Message-ID <[email protected]>
The problem is that libtoolize its putting the copied files in the wrong
directory. I set up a single-user repository using bk setuptool I
imported my project.

In the non-bk original directory running libtoolize -f -c puts the
generated files in the local directory (.). When I run the same command
in the clone directory it puts the copied files from libtool in the
parent directory.

Did I do something wrong when I setup the repository?

Below are the commands I used to setup and import the files.

Stephen 
---------------
bk setuptool configuration:

repository: /home/storri/src/libreverse-REPO
description: ADF library
category: libraries
email: [email protected]
name: 
street: 
city: 
state: 
postal: 
country: 
phone: 
cell: 
pager: 
hours: 
logging: none
keyword: none
compression: gzip
autofix: yes
checkout: none
single_user: storri
single_host: base.torri.org

---------------------
bk import -tplain libreverse ~/src/libreverse-REPO

bash-2.05b$ bk import -tplain libreverse ~/src/libreverse-REPO/
Finding files in /home/storri/src/libreverse
OK
Checking to make sure there are no files already in
        /home/storri/src/libreverse-REPO
OK

Would you like to edit the list of 111 files to be imported? n

Transfering files
        from /home/storri/src/libreverse
        to   /home/storri/src/libreverse-REPO
Checking in plain text files...

Final error checks...
OK
Creating initial changeset (should be +111)
ChangeSet revision 1.2: +111 -0 = 113

---------------



-- 
Email: [email protected]

_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.