[svk-devel] What's the best way to enable non-interactive SVK usage?

[Danny Manners]

In the meantime, you could use expect (http://expect.nist.gov)

On 14/12/2007, Jesse Vincent <jesse at bestpractical.com> wrote:
>
> clkao,
>
> How would you like to make pere's use case work?
>
> 16:36 <pere> TTimo: as far as I can see from the code, there is no way to
> make svk non-interactive.  The get_prompt() function will always try to talk
> to a tty.
> 16:37 -!- kane_ [n=kane at perl.xs4all.nl] has quit []
> 16:37 <TTimo> depends for which operations I suppose
> 16:37 <TTimo> definitely works for my smerge calls
> 16:38 <obra> pere: which interactions are you running into problems with?
> 16:40 <pere> svk init
> 16:41 <pere> but also svk commit, some times (not sure when).
> 16:42 <obra> svk commit shouldn't, if you specify a -m ''
> 16:42 <pere> the script is <URL:
> http://svn.debian.org/wsvn/debian-edu/trunk/src/debian-edu-config/sbin/debian-edu-etc-svk?op=file&rev=0&sc=0>
> 16:42 <pere> obra: it does, if the repository isn't already created, I
> believe.
> 16:42  * obra nods
> 16:42 <obra> iirc, there was a way to force that to non-interactive
> 16:42 <obra> sourcediving
> 16:43 <pere> It would be great.  I want to make svk init non-interactive,
> and svk commit just fail if the repository is missing.
> 16:45 <pere> I've tried to work around the problem using expect, but it
> too fail during debian installation with "The system has no more ptys." :(
> 16:46 <obra> sadly, I am wrong.  I'd like a comment from clkao about how
> he'd like this fixed.
> 16:47 <obra> there's no way to force the non-interactive
> 16:47 <obra> since I know a webgui for svk is in the works, this MUST have
> been dealt with somehow
> 16:47 <pere> right.  it would be great if a fix for it is released soon,
> so I can get it into the next Debian release.
> 16:48 <obra> what's the timing on that look like?
> 16:48 <pere> completely unrelated to this, but related to the script for
> keeping /etc/ in svk.  Is there a way to prune history?  For example, only
> keep changes newer than 2 years, or only keep 12 diffs, one for
>              each month for all changes more than 2 years old?
> 16:49 <obra> that's more of an svn question. and I believe their supported
> answer is svnadmin dump| svndumpfilter|svnadmin load
> 16:49 <pere> obra: everything freezes around may, so I would need a fixed
> package around february/march to be able to fix the etc-svk script.
> 16:49 <obra> ok
> 16:49 <obra> I know we're shooting for a 2.2b1 for Christmas
> 16:49 <obra> I don't know if I can talk cl into the fix by then, but I can
> try
> 16:49 <pere> and 2.2?
> 16:50 <obra> release date in general? "when it's ready"
> 16:50 <pere> :)
> 16:50 <obra> I'm hoping for no more than a month or two.
> 16:50 <obra> there are some really sexy new features
> 16:51 <obra> the big one is more intelligent branch management
> 16:51 <pere> right.  if you need a ref for the non-interactive issue, you
> can use <URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435786 >.
> 16:52 <obra> ok
> 16:52 <obra> I'll see what I can do
> 16:52 <obra> :)
> 16:52 <pere> thanks.
> 16:52 <pere> dumbing down get_prompt() would solve it.  Then I could use
> 'yes | svk init' :)
>
> --
> _______________________________________________
> svk-devel mailing list
> svk-devel at bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.bestpractical.com/pipermail/svk-devel/attachments/20071215/26250f8e/attachment.htm