On Mon, Sep 20, 2010 at 8:53 AM, Koen Deforche <[email protected]> wrote:
> Hey Pau,
>
> 2010/9/19 Pau Garcia i Quiles <[email protected]>:
>> Hello,
>>
>> I was going to start packaging Wt 3.1.5 (I've been unable to do that
>> before due to some health problems) but I found a couple of issues:
>>
>> - Wt 3.1.4 and 3.1.5 both have the same soname (23). It's still 23 in
>> git, too. If you move forward to 25 in git, I will patch the Debian
>> package so that 3.1.5 is 24. Is that OK?
>
> That's okay, yes. I've modified my git copy already.

Only WT_SOVERSION has been bumped to 25, you need to also bump all the
libraries which depend on libwt

>> - libharu: it's not packaged in Debian, therefore I will have to take
>> ownership of it. Given that packaging a new library, get it in the
>> archive, etc represents quite a few hours of work, I'd like to know:
>> are you planning to move from libharu to something else (like it
>> happened with mxml) any time soon?
>
> I believe not. libharu seems to be the only viable option for PDF
> generation. Also, it works really well (there are no major issues we
> found), we only needed one patch for it (which is included in winst
> and was also submitted to libharu). The library is also not as
> fundamental to Wt as the XML library was.

Perfect. I'll start packaging libharu as soon as I finish with Wt 3.1.5

>> Unrelated to packaging Wt 3.1.5: the Wt installer. It is a very nice
>> addition! The only thing I do not like is it uses autotools :-)
>
> Neither do I like autotools, but I really like plain old Makefiles !

Problem with plain old Makefiles is they are not portable :-)

>> therefore it is not available on Windows (which IMHO is the platform
>> where it'd be most useful). I started something like winst using CMake
>> a few months ago (discontinued due to work and health). FILE(DOWNLOAD
>> ... ) and ExternalProject_Add (new in CMake 2.8) would make it
>> possible to build the whole dependency stack on every platform. I'm
>> sorry but I cannot work on this at this moment.
>
> Trying to make it work in one go for Windows too would have really
> held this back.
>
> We realize something like this would even be more useful for Windows,
> and at this point we would not even mind having another solution
> specifically for Windows. At the same time I am not sure how practical
> CMake would be for a cross-platform easy-installer solution since
> relying on CMake 2.8 kind of defeats the purpose of winst for UNIX
> platforms: to checkout Wt on non-cutting edge OS/environments.
> Currently, Wt still builds fine with CMake 2.4.

I see. That should not be a problem. It should be possible to have a
CMakeLists.txt with FILE( DOWNLOAD ... ) and ExternalProject_Add to
replace winst. The only thing you need is something to bootstrap it
for people using CMake < 2.8.

My proposal: have a (very small) .sh for Unix users and a .bat for
Windows users which FTP's to the CMake FTP server and downloads CMake
2.8, then FTP's to webtoolkit.eu and downloads that CMakeLists.txt. On
Windows it is possible to automate the FTP download like this:

-->8----------------------------------------------
echo "Downloading WGet"
               echo "open ftp.mirrorservice.org
anonymous
pass anonymous
binary
get 
/sites/download.sourceforge.net/pub/sourceforge/m/project/mi/mingw/mingwPORT/Current%20Releases/wget-1.9.1-mingwPORT.tar.bz2
bye
" > mingw32.ftp
               ftp -s:mingw32.ftp
-->8----------------------------------------------

Cut and paste that to a .bat and that'll download wget. The FTP server
for CMake is ftp://www.cmake.org/pub/cmake (down now).

On Unix there are so many different FTP clients I think assuming wget
is available (or directly requiring it) would be the safest bet. You
can then download a static, precompiled CMake binary from cmake.org
(or even compile from source :-)

What do you think?

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to