[swift-users] FW: SafeByteArray.h and SafeByteArray.cpp missing...

[Marc Neeley]

I inadvertently sent this to Kevin directly rather than the list. My
apologies.

-----Original Message-----
From: Marc Neeley [mailto:neeleym at ociweb.com] 
Sent: Sunday, March 25, 2012 4:34 PM
To: 'kevin at kismith.co.uk'
Subject: RE: [swift-users] SafeByteArray.h and SafeByteArray.cpp missing...

We are working an example application that uses Swiften libraries and header
files. When we release the example we plan to give readers instructions in
how to build the example application. Many of them will likely not be git
users and the .zip and .tar.gz files that were in the repo were an easy way
to help them get the source if they didn't have a  git client.  Those
compressed files are missing large portions of what is needed from the
source. You mention that it is stable now, so would it be a good time to
create a new zip file with the latest  and place it in the repo or
alternatively would you be okay with us creating a zip file for
redistribution with our example as they will need the header files to build
our example application?  Please advise.

Thanks,
Marc

> -----Original Message-----
> From: k.i.smith at gmail.com [mailto:k.i.smith at gmail.com] On Behalf Of 
> Kevin Smith
> Sent: Sunday, March 25, 2012 4:21 PM
> To: Marc Neeley
> Cc: swift-users at swift.im
> Subject: Re: [swift-users] SafeByteArray.h and SafeByteArray.cpp
missing...
> 
> On Sun, Mar 25, 2012 at 10:18 PM, Marc Neeley <neeleym at ociweb.com>
> wrote:
> >    I’ve noticed that the git repo has a Swiften/Base/SafeByteArray.h 
> > and SafeByteArray.cpp however the swift-1.0.zip and corresponding 
> > .tar.gz file does not have these present. Do these files get 
> > generated or are they simply missing from the zip files?  Is it 
> > required to pull the source only from git?  Please advise.
> 
> Hi there,
>   SafeByteArray.(h|cpp) were added after 1.0. I'd recommend that if 
> you're doing development work with Swiften you grab the source from 
> Git - it's currently stable and many fixes have gone in since 1.0.
> 
> /K