| === DarkLinkXXXX is now known as DarkLinkXXXX_ | ||
| === DarkLinkXXXX_ is now known as XX_DarkLink_XX | ||
| === hloeung is now known as Guest69603 | ||
| === Guest69603 is now known as hloeung | ||
| vila | xnox: :-D | 07:26 |
|---|---|---|
| vila | xnox: ln -s /usr/bin/bzr ~/bin/bar | 07:27 |
| dobey | hi all. how can i verify that a working tree in bzrlib is a lightweight checkout of a branch? | 14:59 |
| mgz | `bzr info`? | 15:05 |
| mgz | or you mean in python? | 15:05 |
| dobey | mgz: with bzrlib in python, yes | 15:13 |
| mgz | workingtree objects have a branch attribute you can inspect to see which it is | 15:15 |
| mgz | and the lightweight checkout chek goes something like: | 15:18 |
| mgz | `tree.user_url != tree.branch.user_url` | 15:19 |
| mgz | dobey: hope that helps | 15:19 |
| dobey | mgz: branch being a bzrlib.branch.Branch? | 15:20 |
| mgz | right, but you get one created for you whenever you construct a tree | 15:20 |
| mgz | you probably want to start: | 15:21 |
| mgz | `d = controldir.ControlDir.open(location); tree = d.open_workingtree();` | 15:21 |
| mgz | and catch some exceptons from open_workingtree | 15:22 |
| dobey | right. already have one because tarmac creates a Branch from the launchpadlib branch, without yet opening the working tree | 15:22 |
| mgz | then you have some fun, because you can't go from less specific to more specific in general | 15:23 |
| mgz | you'd want to reopen the location of the branch as a new object | 15:23 |
| dobey | yeah, it does. | 15:23 |
| dobey | i just wanted to make sure the type was what i thought it was | 15:24 |
| dobey | if user_url is the right thing to check for that, it should do though. thanks | 15:25 |
| === mbarnett` is now known as mbarnett | ||
| === thomi_ is now known as thomi | ||
| === SamB__ is now known as SamB | ||
| === lifeless_ is now known as lifeless | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!