<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div><br></div>Ok, no trouble, deleted deken package.<div><br></div><div><br></div><div><br><br><font face="Courier New, Courier, Monospace" size="2">Mensaje telepatico asistido por maquinas.</font><br><br><div>To: pd-list@lists.iem.at<br>From: zmoelnig@iem.at<br>Date: Sun, 3 Jul 2016 13:07:18 +0200<br>Subject: Re: [PD] [PD-announce] Deken package with missing dlls for old-extended externals (w32).<br><br><pre>hi,<br> <br>On 07/03/2016 08:48 AM, Lucas Cordiviola wrote:<br>> Type “missing” in deken`s search bar.<br>> Then put all dlls in the pd/bin directory.<br> <br>while i appreciate the initiative to provide missing system libraries, i<br>think this is the wrong way to do it.<br> <br>#1 a deken package should be self-contained.<br>if a given deken package lacks a library (e.g. libpthreadGCC3.dll) then<br>it should provide that library itself.<br>(alternatively, deken could be (theoretically; practically i see a<br>number of hurdles) enhanced to explicitely state such dependencies (so<br>installing "foo" would also install "pthreadGCC3")<br> <br>#2 a deken package must be installable by deken. the requierement to<br>"then put all the dlls into pd/bin" contradicts this.<br>until deken can be told to install into pd/bin, i think that though<br>shall not abuse the deken package system for such things.<br> <br>i'd therefore rather have the 'missingDLLs' package removed from<br>puredata.info.<br>we *should* come up with a proper solution for the problem though.<br> <br>fmasdr<br>IOhannes<br> <br></pre><br>_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list</div></div> </div></body>
</html>