On 2/25/2014 12:04 PM, Sergey Alyoshin wrote:
> On Tue, Feb 25, 2014 at 2:20 PM, Markus Rothe <mar...@unixforces.net> wrote:
>> Hello,
>>
>> I am packaging gerbv for my distribution [1] and just wanted to update
>> from 2.6.0 to 2.6.1. I noticed that autogen.sh is not run for the
>> release tarball of 2.6.1.
>
> Yes, it is my mistake.
>
>
>> This is not a big problem, but I just wanted to let you know in case you
>> didn't already noticed. It would be nice if autogen.sh would be run for
>> future release tarballs.
>>
>> Best regards,
>>
>> Markus
>>

On this note, I recently fixed a few things which prevented 'make 
distcheck' from working.  Given the issues with 2.6.1 (release not made 
correctly) I'd like to push out a new version "soon".  Since there have 
been feature changes and not just bug fixes I want to make it 2.7 (the 
teeny # should be reserved for bug fixes only.  Is there any reason I 
should not be trying to find some time soon to do this?  Big outstanding 
bugs?

-Dan


------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Gerbv-devel mailing list
Gerbv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gerbv-devel

Reply via email to