tuxpaint-devel

[Tuxpaint-devel] Tux Paint 0.9.15 release plans

[Bill K. <nb...@so...>]

So I've been putting off releasing Tux Paint 0.9.15 for _WAY_ too long...
mostly because I haven't had time to tidy up some loose ends.

In the coming days I'm going to try to make a list of things I'd like to
see working/fixed/changed in 0.9.15, and then leave the rest for a later
version.

In the meantime, is there anything porters/builders/others need from me?
Can people start making text builds/ports based on the current CVS, so we
can get bugs ironed out before I make a tarball source release?

Thanks!!!

PS to Ben - remind me, what's the trick to make a tarball and NOT include
the CVS and .cvsignore files? ;)

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] Tux Paint 0.9.15 release plans

[Albert C. <aca...@gm...>]

> PS to Ben - remind me, what's the trick to make a tarball and NOT include
> the CVS and .cvsignore files? ;)


For procps, I use variables to explicitly list the files. I build the
tarball before doing my final testing, so I can test what I hope
to release as the final tarball. Makefile code:

#################################################

VERSION :=3D 3
SUBVERSION :=3D 2
MINORVERSION :=3D 5
TARVERSION :=3D $(VERSION).$(SUBVERSION).$(MINORVERSION)

TARFILES :=3D AUTHORS BUGS NEWS README TODO COPYING COPYING.LIB \
Makefile procps.lsm procps.spec v t README.top CodingStyle \
sysctl.conf minimal.c $(notdir $(MANFILES)) dummy.c \
uptime.c tload.c free.c w.c top.c vmstat.c watch.c skill.c \
sysctl.c pgrep.c top.h pmap.c slabtop.c pwdx.c

ifneq ($(MAKECMDGOALS),clean)
ifneq ($(MAKECMDGOALS),tar)
# -- dependency and auto-config stuff goes here --
endif
endif

# let "make" know these aren't real things we will build
.PHONY: clean tar all install

# don't want to type "make procps-$(TARVERSION).tar.gz"
tar: $(TARFILES)
mkdir procps-$(TARVERSION)
(tar cf - $(TARFILES)) | (cd procps-$(TARVERSION) && tar xf -)
tar cf procps-$(TARVERSION).tar procps-$(TARVERSION)
gzip -9 procps-$(TARVERSION).tar

######################################################

[Tuxpaint-devel] bug hunting before release

[Albert C. <aca...@gm...>]

It would be good to check Tuc Paint for bad memory accesses
using the two best tools we have available:

1. Use "valgrind tuxpaint" on a fast x86 machine.

2. Using gcc 4, compile using "-lmudflap -fmudflap". (any CPU is OK)

Re: [Tuxpaint-devel] Tux Paint 0.9.15 release plans

[Ben A. <sy...@sa...>]

On Wed, 2005-09-07 at 20:31 -0400, Albert Cahalan wrote:
> 
>         PS to Ben - remind me, what's the trick to make a tarball and
>         NOT include
>         the CVS and .cvsignore files? ;)
> 
> For procps, I use variables to explicitly list the files. I build the
> tarball before doing my final testing, so I can test what I hope
> to release as the final tarball. Makefile code:

Alternatively, you could use an exclusive approach rather than inclusive
using find and -prune.  Something like:

find . \( -wholename '*/CVS' -o -name .cvsignore \) -prune -o -print

Assuming 'make clean' has run before this, and your clean target is
comprehensive, this will produce a list of only non-junk files to
include in the tarball.

Of course, this doesn't protect against accidentally including
"my_shopping_list.txt" in the tarball.  But then again, it doesn't
require you keep TARFILES up-to-date.  Choose whichever method you think
is less likely to cause you grief maintaining.

Ben

Re: [Tuxpaint-devel] Tux Paint 0.9.15 release plans

[Bill K. <nb...@so...>]

On Thu, Sep 08, 2005 at 09:49:39AM -0300, Ben Armstrong wrote:
> Alternatively, you could use an exclusive approach rather than inclusive
> using find and -prune.  Something like:
> 
> find . \( -wholename '*/CVS' -o -name .cvsignore \) -prune -o -print

I've added a "make release" target.  Thx! :)

-bill!

Re: [Tuxpaint-devel] Tux Paint 0.9.15 release plans

[Ben A. <sy...@sa...>]

On Sun, 2005-10-09 at 17:10 -0700, Bill Kendrick wrote:
> I've added a "make release" target.  Thx! :)

        @cd .. ; \
         find tuxpaint-$(VER_VERSION) -follow \
             \( -wholename '*/CVS' -o -name .cvsignore \) \
             -prune -o -type f -print0 | \
           xargs -0 tar -czvf tuxpaint-$(VER_VERSION).tar.gz 

What creates the tuxpaint-$(VER_VERSION) tree?  I could find no target
that does this.  Perhaps you created this tree manually?  The "release"
target needs to either do this itself or depend on a target that does
this.

Ben

Re: [Tuxpaint-devel] Tux Paint 0.9.15 release plans

[Bill K. <nb...@so...>]

On Mon, Oct 10, 2005 at 08:43:44AM -0300, Ben Armstrong wrote:
> On Sun, 2005-10-09 at 17:10 -0700, Bill Kendrick wrote:
> > I've added a "make release" target.  Thx! :)
> 
>         @cd .. ; \
>          find tuxpaint-$(VER_VERSION) -follow \
>              \( -wholename '*/CVS' -o -name .cvsignore \) \
>              -prune -o -type f -print0 | \
>            xargs -0 tar -czvf tuxpaint-$(VER_VERSION).tar.gz 
> 
> What creates the tuxpaint-$(VER_VERSION) tree?  I could find no target
> that does this.  Perhaps you created this tree manually?  The "release"
> target needs to either do this itself or depend on a target that does
> this.

Ah, for the moment, I've simply hacked it by doing this:

  mv tuxpaint tuxpaint-0.9.15

But yeah, it would be good if there were a target that duplicated the
source tree into a versioned directory.  Maybe using that 'find' to copy
only the files we want, and then a simple 'tar' to roll it together.

-bill!

Re: [Tuxpaint-devel] Tux Paint 0.9.15 release plans

[Ben A. <sy...@sa...>]

On Mon, 2005-10-10 at 08:43 -0300, Ben Armstrong wrote:
> On Sun, 2005-10-09 at 17:10 -0700, Bill Kendrick wrote:
> > I've added a "make release" target.  Thx! :)
> 
>         @cd .. ; \
>          find tuxpaint-$(VER_VERSION) -follow \
>              \( -wholename '*/CVS' -o -name .cvsignore \) \
>              -prune -o -type f -print0 | \
>            xargs -0 tar -czvf tuxpaint-$(VER_VERSION).tar.gz 
> 
> What creates the tuxpaint-$(VER_VERSION) tree?  I could find no target
> that does this.  Perhaps you created this tree manually?  The "release"
> target needs to either do this itself or depend on a target that does
> this.

By the way, I don't really like this business of making things outside
of the current tree.  The way I have most often see other packages
handle this is to create a directory called "build" which is populated
with the build target directories, something like:

Index: Makefile
===================================================================
RCS file: /cvsroot/tuxpaint/tuxpaint/Makefile,v
retrieving revision 1.79
diff -r1.79 Makefile
125c125,141
< release:
---
> releaseclean:
> 	@echo
> 	@echo "Cleaning release directory"
> 	@echo
> 	@rm -rf build/tuxpaint-$(VER_VERSION)
> 
> releasedir: releaseclean
> 	@echo
> 	@echo "Creating release directory"
> 	@echo
> 	@mkdir -p build/tuxpaint-$(VER_VERSION)
> 	@find . -follow \
> 	     \( -wholename '*/CVS' -o -name .cvsignore -o -name 'build' \) \
> 	     -prune -o -type f -exec cp --parents -vdp \{\} build/tuxpaint-$(VER_VERSION)/ \;
> 
> 	
> release: build/tuxpaint-$(VER_VERSION)
128,135c144,147
< 	@
< 	@make clean
< 	-@rm -f ../tuxpaint-$(VER_VERSION).tar
< 	@cd .. ; \
< 	 find tuxpaint-$(VER_VERSION) -follow \
< 	     \( -wholename '*/CVS' -o -name .cvsignore \) \
< 	     -prune -o -type f -print0 | \
< 	   xargs -0 tar -czvf tuxpaint-$(VER_VERSION).tar.gz 
---
> 	@echo
> 	-@rm -f build/tuxpaint-$(VER_VERSION).tar.gz
> 	@cd build ; \
> 	    tar -czvf tuxpaint-$(VER_VERSION).tar.gz tuxpaint-$(VER_VERSION)

Nothing cleans "build" here because there might be a build from a prior
version still kicking around.  Maybe we need a reallyclean target that
nukes absolutely everything, including all build dir contents.

Ben