<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'><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><i>>deken has a plugin-system to add additional sources for externals. the</i></div><div><i>>only one that i know of is for "apt", which allows you to search/install</i></div><div><i>>the Debian/Ubuntu/... packages.</i></div></blockquote><div><br></div><div>Lets put aside this option for clarity as I don`t get it. This downloads all sources and compiles on target machine? Where does the 3th pty Lib goes?</div><div><br></div><div>Lets focus on this as is more useful for normal users:</div><div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><i>>and of course, you can still install "normal deken packages" (pre-built</i></div><div><i>>binaries from puredata.info).</i></div></blockquote><div><br></div><div><br></div><div>I think that NOT SHIPING 3th pty Libs contradicts *your* very good idea that a Deken pkg must be “self operational”.</div><div>Someone wants to distribute a patch and includes the external and the 3th pty Lib, the patch simply opens and works, thats all.</div><div><br></div><div>he/she has simply got those files from the Deken pkg.</div><div><br></div><div>Why NOT shiping 3th pty libs on Linux?</div><div><br></div><div><br></div><br><font face="Courier New, Courier, Monospace" size="2">Mensaje telepatico asistido por maquinas.</font><br><br><div><br></div> </div></body>
</html>