[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#832941: RFS: 4pane



Dear Sean,

I'd not lost interest, just slowed down during the stretch freeze. I've now
uploaded an altered d/

>> Many thanks for the offer. I don't mind packaging Bakefile, and it shouldn't
>> be difficult to do.
>> 
>> However will it be accepted into debian? The project is moribund...
>> Do you feel this alters the situation?
>If it hasn't bitrotted after 3 years, and you're willing to fix
>non-wishlist bugs that get reported to the Debian bug tracker, it would
>be fine to upload Bakefile.

I did create a Bakefile package but found that Bakefile segfaults with the
stretch version of python. Though by coincidence a fix was mentioned elsewhere a
few days later so it could be made to work, I was sufficiently discouraged that
future 4Pane releases will probably switch to automake.

I've therefore removed all Bakefile traces from the source repo and substituted
an automake build system. This autoreconfs and builds successfully.

I hope you will be happy with this alternative, but if not I'll fix the
potential Bakefile package.

>>3. In a previous e-mail I explained why I think it would be clearer to
>>call the wxWindows license "GPL-2+ or wxWindows-3.1+".  So far as I can
>>tell you never responded to that -- please consider the points I made.
>>Unless I'm missing something, it would make d/copyright clearer.
>
>I think I did, but anyway:
>In wxWindows circles the licence is invariably referred to as the wxWindows
>one, often with the explanation that it's GPL-2 plus an exception. It's also
>used in the libwxgtk3.0 packages' d/copyright. However I don't have any
>expertise in such things and I'm happy to change it if it's thought necessary.


Regards,

David Hart


Reply to: