Re: [Wigwam-devel] wigwam presentation material?

[Mike A. <as...@lo...>]

Heya,

> What's going on with wigwam?  are you going to continue using it?

We just started using it here at Lokku (http://www.lokku.com).  Some of 
my colleagues where not impressed by a project that has so little 
development and no evident use, but I compelled them by force of 
argument (it took be 3 weeks to get a working playpen) and they seem to 
be coming around.

> chroots and binary launching

Sounds a bit like ypackage.

> wigwam 4 is better and even more obscure because no one switched to it.

We are using SVN, so the wig3 launch tools aren't of use to use, but we 
get by nicely with tarballs and symlinks.  I didn't realize that wig4 
could be used with other version control systems.  That shivers my 
fucking timbers.  Will check it out.

> how difficult it is to use  it's package archive

My only major problem here is that there is no smooth upgrade procedure 
for when packages change.  That is, if I change the project-packages, I 
can't signal others to uninstall/install the old/new version. 
Otherwise, the simple packages work well enough for us.  Builds failing 
because of inter-distro eccentricities are more of a problem than 
anything specific to The Wam.

> binary packaging

Can't you specify support archs for a package?  You _could_ just make 
raw packages and copy them straight into ext, if you're that keen.

> I love that it lets me dev on osx and launch to linux

We do the same.  Modulo the bit of weirdness, it all works well.

Wigwam is the only tool I know about that solves a particular and common 
set of problems.  I felt a bit old school picking it up again, but I 
didn't see a good alternative.  Is there something else out there that 
competes?

-mike