| 2007-08-28 09:09:07 |
Jari Aalto |
description |
DESCRIPTION
Local checkout command records absolute paths even in relative
checkout situation. This means that the checkout is unmovable to
another directory.
AN EXAMPLE
Directory hierarchy:
/usr/share/development
|
+- my-tools/
|
+- one/one-1.0/
+- two/two-1.23/
+- three/three-2.0.1/
At one/one-1.0 directory and likewise in every other package
directory:
$ bzr co ../../my-toools
Then, there is need to move the project:
mv /usr/share/development /usr/share/ports/development
IMPLICATIONS
All the relative checkous become invalid when directories are moved.
This is very common in situation.
Another exmaple woud be:
- A package is downloaded
- A port is tried (tools "'checked out" into it)
- If success, move whole project to "good" directory
If failure, move to staging "bad" or "todo" directory for
further examination.
To bzr to remember and use relative paths (IF user used those), would
be very important. |
DESCRIPTION
Local checkout command records absolute paths even in relative
checkout situation. This means that the checkout is unmovable to
another directory.
AN EXAMPLE
Directory hierarchy:
/usr/share/development
|
+- my-tools/
|
+- one/one-1.0/
+- two/two-1.23/
+- three/three-2.0.1/
At one/one-1.0 directory and likewise in every other package
directory:
$ bzr co ../../my-toools
Then, there is need to move the project:
mv /usr/share/development /usr/share/ports/development
=======
COMMENTS
All the relative checkous become invalid when directories are moved.
Another exmaple woud be:
- A package is downloaded
- A port is tried (tools "'checked out" into it)
- If success, move whole project to "good" directory
If failure, move to staging "bad" or "todo" directory for
further examination.
To bzr to remember and use relative paths (IF user used those), would
be very important.
|
|
