Re: [fossil-users] Stability of fossil test-name-to-id

2014-08-20 Thread org.fossil-scm.fossil-users
'Lo.

On 2014-08-19T21:17:18 +0200
Stephan Beal sgb...@googlemail.com wrote:

 You might be interested in a standalone alternative:
 ...
 
 and has already been created as a standalone binary with documented
 semantics:
 
 http://fossil.wanderinghorse.net/repos/libfossil/doxygen/fossil-core_8h.html#a265d03fe1e040d7068679f9b2a4d1a11

Looks good, certainly. Problem in my case is that I'd either have to
write language bindings (as I'm not working from C), or require the
person using my program to have installed your standalone utilities.

I'm trying to stick to either calling the fossil binary directly, or
piping SQL into fossil sqlite in the worst case.

Am I to assume that test-name-to-id is definitely not to be depended
upon?

M
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Stability of fossil test-name-to-id

2014-08-20 Thread Stephan Beal
On Wed, Aug 20, 2014 at 8:44 PM, org.fossil-scm.fossil-us...@io7m.com
wrote:

 I'm trying to stick to either calling the fossil binary directly, or
 piping SQL into fossil sqlite in the worst case.


Aha! ... i _thought_ we had an sqlite binding to that function, but
apparently we don't (libfossil does ;). i've added that to the todo list
(in the case that it really is missing), so you could so something like:

echo select sym2rid('trunk'); | fossil sqlite
echo select sym2uuid('trunk'); | fossil sqlite


 Am I to assume that test-name-to-id is definitely not to be depended
 upon?


Nothing named test- should be depended upon. Those are all tests written
during the implementations of various features. That particular one just
happens to be extraordinarily useful. We should certainly consider
upgrading it to real command status.


-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Stability of fossil test-name-to-id

2014-08-20 Thread Richard Hipp
On Wed, Aug 20, 2014 at 2:44 PM, org.fossil-scm.fossil-us...@io7m.com
wrote:


 Am I to assume that test-name-to-id is definitely not to be depended
 upon?


Probably test-name-to-id won't just go away.  If you encounter problems, it
will likely be because we enhance the command to output additional
information, which then breaks your parsing logic.  Or the command might be
promoted to a supported command by removing the test- prefix.

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Stability of fossil test-name-to-id

2014-08-20 Thread Stephan Beal
On Wed, Aug 20, 2014 at 8:50 PM, Stephan Beal sgb...@googlemail.com wrote:

 Aha! ... i _thought_ we had an sqlite binding to that function, but
 apparently we don't (libfossil does ;). i've added that to the todo list
 (in the case that it really is missing), so you could so something like:


 echo select sym2rid('trunk'); | fossil sqlite
 echo select sym2uuid('trunk'); | fossil sqlite



Nevermind - now i see why we don't have one. The sqlite handle used by that
feature is not fossil-aware. The fossil global state gets shut down before
the sqlite shell is run (maintained as part of the sqlite project). So i
can't add this without a notable overhaul (which doesn't seem worth the
effort).

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Stability of fossil test-name-to-id

2014-08-20 Thread org.fossil-scm.fossil-users
On 2014-08-20T14:51:30 -0400
Richard Hipp d...@sqlite.org wrote:
 
 Probably test-name-to-id won't just go away.  If you encounter problems, it
 will likely be because we enhance the command to output additional
 information, which then breaks your parsing logic.  Or the command might be
 promoted to a supported command by removing the test- prefix.

On 2014-08-20T20:50:26 +0200
Stephan Beal sgb...@googlemail.com wrote:

 Nothing named test- should be depended upon.


Ok, thanks to you both!

I'll use SQL for now. Needless to say, I'd love to see this become a
supported command, ideally just producing a single artifact ID as
output to avoid having to parse anything. I'm mainly just using this
information to determine whether the tip of the repository has changed
since I looked at it last.

M
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Stability of fossil test-name-to-id

2014-08-19 Thread org.fossil-scm.fossil-users
Hi.

I'm writing a program that depends on the functionality of
test-name-to-id. Given that the command is completely undocumented and
doesn't appear in any help texts, is that sufficient warning to suggest
that the command may be removed at any moment and shouldn't be used for
anything?

I could open the repository and perform the SQL query manually, but the
temptation to use a command that's already written and known to work is
tempting...

M
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Stability of fossil test-name-to-id

2014-08-19 Thread Stephan Beal
On Tue, Aug 19, 2014 at 9:12 PM, org.fossil-scm.fossil-us...@io7m.com
wrote:

 I'm writing a program that depends on the functionality of
 test-name-to-id. Given that the command is completely undocumented and
 doesn't appear in any help texts, is that sufficient warning to suggest
 that the command may be removed at any moment and shouldn't be used for
 anything?


You might be interested in a standalone alternative:

[stephan@host:~/cvs/fossil/fossil]$ f-resolve trunk current prev rid:1
ee46563cbdc28face0215bc1a5cf81f0b589d88a   26866 trunk
ca5d6f2b482bd08c58886b0fd4a96aaffc56f893   26901 current
d8902124d481ced2a800fc3ec4d3212640c25563   26899 prev
a28c83647dfa805f05f3204a7e146eb1f0d90505   1 rid:1

that's available in the libfossil sources:

http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/wiki?name=f-tools



 I could open the repository and perform the SQL query manually, but the
 temptation to use a command that's already written and known to work is
 tempting...


and has already been created as a standalone binary with documented
semantics:

http://fossil.wanderinghorse.net/repos/libfossil/doxygen/fossil-core_8h.html#a265d03fe1e040d7068679f9b2a4d1a11

:)

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users