http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1195
------- Comment #7 from jmayer@xxxxxxxxx 2006-11-02 21:39 GMT -------
OK, just had a look into it and the svn authors are strongly against reading
entries directly. Maybe going back to svnversion would be the right step.
I have sent an email to wireshark-dev discussing it.
Just for the fun of it - the last lines of the conversation on #svn-dev:
22:28 < Terman> ok, I'll take the topic to wireshark-dev and see whether
requirering svnversion in $PATH is OK
22:28 <@davidjames> Woohoo, another project who *isn't* parsing Subversion
working copies! :)
22:28 < Terman> davidjames: not yet ;-)
22:29 < dionisos> davidjames: we should keep changing the wc format and entries
file. They will stop eventually :-)
22:30 <@davidjames> perhaps we can encrypt the entries file ;)
22:30 < dionisos> ooohhh! nice!
22:31 < JMcA> even something as trivial as rot-13, but something equally as
trivial and *different* for each release
22:31 <@rooneg> maybe we could encode it in some incredibly obscure character
encoding that nobody has a library for
22:31 <@davidjames> EBCDIC
22:31 < sabor> morse :)
22:32 < pburba> Hey now, don't make fun of CRAPCDIC, it's because of it that I
have a J-O-B
22:32 < JMcA> XOR it with the repeating string of the svn repository revision
number of the release
22:35 < dionisos> lundblad should have reserved the first X lines for a warning
message (from which *we* could find out how the rest of the file is encrypted)
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.