[bakefile-devel] ANN: 0.2.6 pre-release

[Vaclav Slavik]

Hi,

I uploaded pre-release packages for 0.2.6:
https://sourceforge.net/project/showfiles.php?group_id=83016&package_id=85308&release_id=671271

The changelog is here:
http://www.bakefile.org/browser/bakefile/trunk/NEWS

As usual, the plan is to release 0.2.6 in a week or so if there are no
non-trivial problems with these packages.

Regards,
Vaclav

[Francesco Montorsi]

Hi,

Post by Vaclav Slavik
Hi,
https://sourceforge.net/project/showfiles.php?group_id=83016&package_id=85308&release_id=671271
http://www.bakefile.org/browser/bakefile/trunk/NEWS
As usual, the plan is to release 0.2.6 in a week or so if there are no
non-trivial problems with these packages.

it would be very nice for wxCode devs (and other wxWidgets devs) to have
http://www.bakefile.org/ticket/236 in this release...

In fact currently lots of bakefiles.bkgen files for wx-based apps contains a
line like:

<add-flags>-I %WXWIN%/build/bakefiles/wxpresets</add-flags>

The WXWIN env var is very useful to avoid using absolute paths in files which
are placed in the SVN repo.

Also, many devs don't like / don't want to know about the build system and thus
using the environment variable is better than using <include
file="Bakefiles.bkgen.local" ignore_missing="1"/> and put the <adds-flags>-I
myabsolutepath</add-flags> in the Bakefiles.bkgen.local...

Also the patch makes bakefile_gen a little smarter about expression evaluation...

Francesco

[Vaclav Slavik]

Post by Francesco Montorsi

Post by Vaclav Slavik
As usual, the plan is to release 0.2.6 in a week or so if there are no
non-trivial problems with these packages.

it would be very nice for wxCode devs (and other wxWidgets devs) to have
http://www.bakefile.org/ticket/236 in this release...

As always, no non-critical bugs will be fixed between pre1 and final
release and new features will *definitely* not be added. The point of
prereleases is to verify nothing is broken, any non-trivial additions
would negate that testing.

Post by Francesco Montorsi
Also, many devs don't like / don't want to know about the build system and thus

This doesn't make sense: developers *by definition* have to know about
the build system. And developers who don't want to bother with Bakefile
will use the generated makefiles -- that's the whole point of it!

Vaclav

[Scott Bailey]

Vaclav,

Just built the deb package... A couple things had to change to build an
error free Lenny deb, but they aren't show stoppers.

First, I am NOT a package maintainer and not especially conversant in the
debuild process. Nonetheless, the 'debian/rules' file need this change.
dh_python is deprecated, I think dh_pysupport is probably the correct
choice. Of course, documentation needs to change, but maybe this should
wait for Vadim?

Having said that, I will look into the Debian Maintainer process to see
about getting Bakefile into Squeeze, the next release.


Second, the output of *grep ^[#][\!] `find | grep [.]py\$`* highlights an
interesting issue. Here is the output:
./src/empy/em.py:*#!/usr/local/bin/python*
./src/bakefile_gen.py:#!/usr/bin/env python
./src/bakefile.py:#!/usr/bin/env python
./macosx/buildpkg.py:#!/usr/bin/env python
./build/python-makezip.py:#!/usr/bin/env python
./autoconf/merge-scripts.py:#!/usr/bin/env python

Guess what file isn't on my system?

I'll begin testing the pre-release on Monday.

Thanks again for this tool!

SB

[Vaclav Slavik]

Post by Scott Bailey
dh_python is deprecated, I think dh_pysupport is probably the correct
choice. Of course, documentation needs to change, but maybe this
should wait for Vadim?

Either him or you, I'm of no use when it comes to Debian packaging I'm
afraid.

Post by Scott Bailey
Guess what file isn't on my system?

And guess which one doesn't have the executable bit set? empy/em.py is
only used as importable Python module by writer.py.

Post by Scott Bailey
I'll begin testing the pre-release on Monday.

Thanks!
Vaclav

[Scott Bailey]

Post by Vaclav Slavik
Either him or you, I'm of no use when it comes to Debian packaging I'm
afraid.

Post by Scott Bailey
Guess what file isn't on my system?

And guess which one doesn't have the executable bit set? empy/em.py is
only used as importable Python module by writer.py.

debuild threw a warning. I'm guessing the appropriate action is to remove
the hashbang line? I did this for my test....

If Vadim doesn't step in, I'll provide my changes. Do you want the patch in
Trac?

[Vaclav Slavik]

Post by Scott Bailey
debuild threw a warning. I'm guessing the appropriate action is to
remove the hashbang line?

I didn't want to do any changes compared to upstream, but if it shuts
debuild up, yes.

Post by Scott Bailey
I did this for my test....
If Vadim doesn't step in, I'll provide my changes. Do you want the
patch in Trac?

It's preferred, yes.

TIA!
Vaclav

[Scott Bailey]

Vaclav,

I wrote ticket 244 <http://www.bakefile.org/ticket/244> for the Debian build
and included 2 patches.

No regressions using gnu or xcode2. I can't easily test msvs2005prj this
week.

FYI, I use xcode2 changes that are NOT ready for trunk. So my testing of
xcode2 is not entirely pure... Still, I am happy with 0.2.6.

SB

Post by Vaclav Slavik

Post by Scott Bailey
debuild threw a warning. I'm guessing the appropriate action is to
remove the hashbang line?

I didn't want to do any changes compared to upstream, but if it shuts
debuild up, yes.

Post by Scott Bailey
I did this for my test....
If Vadim doesn't step in, I'll provide my changes. Do you want the
patch in Trac?

It's preferred, yes.
TIA!
Vaclav
------------------------------------------------------------------------------
_______________________________________________
Bakefile-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bakefile-devel