Hello IOhannes,<br><br>thanks for your answer... <br><br><div class="gmail_quote">On Mon, Sep 21, 2009 at 4:08 AM, IOhannes m zmoelnig <span dir="ltr"><<a href="mailto:zmoelnig@iem.at">zmoelnig@iem.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Anderson Goulart wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all,<br>
</blockquote><div class="im">
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
puredata-ext-XX - package containing a single external<br>
puredata-abs-XX - package containing a single abstraction<br>
</blockquote>
<br></div>
why do you want to separate them? </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
how does a "single external" differ (substantially) from a "single abstraction"? (esp. since .deb takes care of platform-in/dependency)<br>
<br></blockquote><div><br>Well, this is just an ideia and we can decide to use names like puredata-xxx, where xxx is the name of external/abstraction. What I want here is to discuss the conventions about packaging things related to Pd. <br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
do you really want to distribute a _single_ file with an entire .deb or do you rather mean "library"?<br>
<br></blockquote><div><br>Maybe we can distribute a "library" if those externals/abstractions are related. But if they are different, with different upstream authors, with different dependencies and different funcionalities, I think distribute an entire .deb is better than put it together in a library. <br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
how does this integrate into the already existing debian infrastructure for Pd? e.g. with naming schemes like "pd-zexy" or "pd-gem" (that is: why do we want to reinvent the wheel?)<br>
<br></blockquote><div><br>I am not a debian developer, but I am sure we can talk to them to upload all packages to the official repo. The naming conventions are just suggestions and we can use pd-xxx instead of puredata-xxx. The main idea of this email is to separate pd-extended into some .deb packages to become more clear and easier to maintain to many architectures and distribution versions. </div>
</div><br><br>bye, global<br>