<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>>and of course, whoever creates a deken package is encouraged to do</i></div><div><i>>whatever possible within the current format to get their thing running</i></div><div><i>>as smooth as possible (and if this includes bundling 3rd party libraries</i></div><div><i>>for 5 OSs and 18 architectures, then so be it).</i></div><div><i>></i></div><div><i>>what my opposition is directed at is adding cruft to the pd-core to</i></div><div><i>>allow for deviant packaging practices.</i></div></blockquote><div><br></div><div>What will be the problem for a linux system to look for the 3th party Lib in the same folder as the ext (which needs it) if it can't find anywhere else in the local system?</div><div><br></div><div>IYO this is adding cruft?</div><div><br></div><div>We are discussing Deken dependencies and abs sharing.</div><div><br></div><div>And also I`m following *your* good idea that a deken pkg must be “self operational”.</div><div><br></div><div>Lets have the “normal ubuntu” users a more practical way of Pd while “super users” like you can do all the “$ sudo apt-get install pd-deken-apt” thing.</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>