Re: [Audacity-devel] Re: [Audacity-help] cd version

[Dave F. <dav...@at...>]

On Sunday 16 February 2003 09:59 pm, Joshua Haberman wrote:
> On Sun, 2003-02-16 at 21:43, Dave Fancella wrote:
> > As a subscription, then, I'll be more than happy to create a dist
> > directory for cvs that would be basically:
> >
> > dist/iso  -  the root directory of the CD
> > dist/packaging  -  Basically just a sxw file or rtf for printing a la=
bel
> > to be put on a CD and maybe a jewel box liner.
>
> Preferably in a different CVS module -- no reason why people should hav=
e
> to download that stuff for a regular source code checkout...

Well, right now I'm leaning towards using the xburnpro service that Domin=
ic=20
gave the link for, and if we do that then we'll have little/no control ov=
er=20
packaging.  It also means that all that would need to be done is to setup=
 the=20
account with xburnpro, and then release builds placed on the website at t=
he=20
URLs that xburnpro will retrieve them.  Then the CD will always have the=20
latest stuff, and the project need not worry about sales/shipping.  It wo=
uld=20
be automated.

OTOH, we'd have no control over packaging.  They would install their own=20
proprietary CD-browsing software with advertising, and there's no guarant=
ee=20
right now that Linux users would be able to use the CD, even if there is =
a=20
Linux build and source code on the CD.  It's a good bet, but xburnpro doe=
sn't=20
support Linux, so there's no guarantee.  We'd also be limited in what kin=
d of=20
cool stuff to include.  When audacity becomes a "larger" account with=20
xburnpro, there would be options to pull the xburnpro software off the CD=
,=20
and possibly a lot more control over packaging, but still the OS issue. =20
Unless the OS issue is only about their proprietary CD-browsing software,=
 in=20
which case when we have complete control over it we (or I) would code up=20
something to run on all OSs.  (It's not unreasonable to throw together a=20
wxPython interface and then include python binaries for each platform to =
run=20
it)

I'll throw something together to ship this lady that wants a CD using the=
 most=20
recent 1.1.x Windows release and the stable 1.0 release and make a tarbal=
l. =20
If she can download an iso image and burn it, I can make the iso image fo=
r=20
her to download, no problem.  Anyone know where I can grab an archive of =
free=20
VST plugins to stick in there?  Also, has anyone experimented with compil=
ing=20
LADSPA plugins with cygwin or something and plugging them into Audacity?

Otherwise, though, Josh, I agree that it should be a separate root-level=20
module.  There's the possibility of having 100MB+ of binary stuff that wo=
uld=20
really screw over any dialup CVS users.  It would even inconvenience peop=
le=20
with faster connections....

Dave

> Josh
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

--=20
"I slipped inside the oval office,
I slipped in oh so fast,
Grabbed the president by the necktie
And wiped my funky ass, hey"
                -Soulhat, "Bonecrusher"