<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Just to add one cent, it looks simpler to put everything on same package, and should be faster for making server backups.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><div style="font-size:100%">Patrice Colet </div></div> <br><br><br>-------- Message d'origine --------<br>De : fls@rendera.com.br <br>Date : 07/02/2013 5:01 (GMT+00:00) <br>A : pd-list@iem.at <br>Objet : Re: [PD] Plugin auto install feature to Pure data <br> <br><br>Thanks Hans!<br><br>Just one doubt: How does it work for different architectures? Should we<br>pack windows, linux and Mac in different packages? Or can we include them<br>in one package and the installer copies just the right one?<br><br>cheers<br><br>f schiavoni<br><br>> This stuff is already pretty well defined in the library template and the<br>> *-meta.pd file. I think the meta file would be the place to add things<br>> like<br>> dependencies also.<br>><br>> http://puredata.info/docs/developer/Libdir<br>> http://puredata.info/docs/developer/LibraryTemplate<br>><br>> .hc<br>><br>> On 02/05/2013 04:11 PM, fls@rendera.com.br wrote:<br>>> I agree that depencencies should not install libs. Since it seems to be<br>>> the biggest problem, maybe it should be postponed.<br>>><br>>> Yes, the repository maintenance can be solved latter too. Let's first<br>>> have<br>>> a repository and then think about the best way to keep it on date. :-)<br>>><br>>> I don't have skills with TCL but I agree that it is a good choice. Is<br>>> there how to open zip/tar/something files in TCL? If it can open the<br>>> package, it's perfect.<br>>><br>>> IMO, the first step is to install locally. Define a package structure, a<br>>> package header and the install script. Probably it can be used by the<br>>> remote install.<br>>><br>>> I suggest the following package structure:<br>>> /content.txt<br>>> /bin/files <-to compiled files (architecture dependent)<br>>> /help/files <-to help files (architecture independent)<br>>> /tcl/files <-to gui files (architecture independent)<br>>><br>>> This structure should be compacted / grouped in a file with some name<br>>> convention like package_name.version.pd_pkg.<br>>><br>>> The content.txt can be as follow:<br>>> name:<br>>> author:<br>>> version:<br>>> key-words:<br>>> web-site:<br>>> license:<br>>> flavor:<br>>> dependencies:<br>>> instructions:<br>>><br>>> The install script should select a package, open it, copy the external<br>>> to<br>>> the external dir, copy the help and tcl files to the correct folder,<br>>> rename the content.txt to the package name + version and copy it to an<br>>> folder designed for this kind of file.<br>>><br>>> Cheers<br>>><br>>> f schiavoni<br><br><br>_______________________________________________<br>Pd-list@iem.at mailing list<br>UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list<br></body>