[PD] PD Launcher/External Manager

[Hans-Christoph Steiner]

This is a great idea, something I was planning on working on this 
summer.  I'd like to contribute if possible.  Perhaps we can put it in 
the CVS and collaborate.

As for distributing the externals, I think rather than building our own 
distribution system, we should use what's out there for each OS.  
Debian and RedHat have very nice existing methods, and the externals in 
the SourceForge CVS can be compiled into a set of Debian packages right 
now.  They just need to be submitted to the Debian and/or DeMuDi 
repository.  It shouldn't be too hard to add RedHat/PlanetCCRMA to 
that, but currently Nando at CCRMA does that outside of the CVS.

For Windows and OS X, if we make installer packages for the same sets 
of externals as the Debian packages, that will greatly simplify things. 
  But the biggest thing that would improve the situation would be to 
have all of the externals in the CVS.  Then they would be included in 
the existing packages, or if necessary, they can be made into their own 
package.

Think of it this way: if we had all of the externals that didn't have 
lib dependencies in the CVS, they could all be included in the main 
externals package in the CVS and they would all be installed with that 
package.  The key omissions that I can think of off the top of my head 
are the collections of Olaf Matthes, Krzysztof Czaja, Thomas Musil, 
Dave Sabine, and Yves Degoyon; there are others as well, who's objects 
are an important addition to anyone's pd install, and I hope that 
anyone who writes externals for pd will contribute them to the CVS.

So to encourage others to join the CVS, I am going to configure access 
control lists in the CVS so that devs who choose to can restrict write 
access to their code in the CVS.  I am also willing to upload people's 
code and help with setting up CVS access.

.hc

On Tuesday, May 13, 2003, at 13:00 America/New_York, bbogart at ryerson.ca 
wrote:

>
> If someone wanted to upload built versions of the stable externals in 
> CVS, as tgz and zip files, for all platforms to a ftp server, then 
> that would be a LOT easier for the tool to do. (download and extract, 
> but then you depend on extraction tools, whats the average size of the 
> externals? (for all platforms?)
>
> I'm thinking the double pane idea would work better from a usability 
> standpoint, opinions?
>
> B.
>
> ----- Original Message -----
> From: Marc Lavallée <odradek at videotron.ca>
> Date: Tuesday, May 13, 2003 9:51 am
> Subject: Re: [PD] PD Launcher/External Manager
>
>> David McCallum wrote :
>>> My Pd launcher's no more than a custom DOS .bat file that let's
>>> you turn Framestein and ASIO drivers on/off at runtime.
>>
>> I use the same technique in Linux with a shell script.
>>
>>> And as a windows user I have to ask this, how cross-platform are
>>> you intending this to be?
>>
>> Tcl/Tk. The launcher would list the externals with their descriptions,
>> and checkboxes would activate them. If an internet source is
>> provided it
>> would first download and install the externals. Isn't there a Windows
>> mechanism to install softwares from the network?
>>
>> --
>> Marc
>>
>> "L'homme n'est pas fait pour travailler, la preuve c'est que cela le
>> fatigue." (Voltaire)
>>
>> _______________________________________________
>> PD-list mailing list
>> PD-list at iem.kug.ac.at
>> http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
>>
>
>
> _______________________________________________
> PD-list mailing list
> PD-list at iem.kug.ac.at
> http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list