<div class="gmail_quote">On Sat, Jul 31, 2010 at 6:24 PM, Aleksey Lim <span dir="ltr"><<a href="mailto:alsroot@member.fsf.org">alsroot@member.fsf.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<br>
<br>
Just wondering, how to name Sugar Packages.<br>
<br>
The reasons to not reuse "package" name - it is not regular<br>
(GNU/Linux distributions) packages, because:<br>
<br>
* primal deploying model is decentralized (via 0install) not centralized<br>
which is the core point of regular distros<br>
* sugar "packages" still could be represented as regular packages to<br>
support centralized sugar distributions but in that case it will<br>
look like tunneling, e.g., ssh tunnels via http<br>
* in most cases, "packages" will contain results of doer experiments,<br>
e.g., not fully tested/QAed/etc stuff like packages in regular<br>
distributions (at least in stable distro releases)<br>
* in most cases, "package" maintainers will be their developers<br>
because there is no need in any "packaging" work except supporting<br>
an analog of <a href="http://activity.info" target="_blank">activity.info</a> file (for activities)<br>
<br>
The reasons to not reuse "activity" name:<br>
<br>
* "packages" might contain not only activities but libraries, other<br>
(not)well distro packaged dependencies, .xol content or sugar itself<br>
* it is about deploying content not about its quality<br>
<br>
The reasons to not reuse "bundle" name:<br>
<br>
* distribution will happen not only (or, usually, not at all) via bundles<br>
(e.g. .xo bundles)<br>
<br>
And the last but not least :) reason, it would be really cool to have special<br>
name for sugar packages, e.g, Ruby has "gems", Python has "eggs".<br>
<font color="#888888"><br>
--<br>
Aleksey</font></blockquote><div><br></div><div class="gmail_quote"><div>Sugar "cubes" come to mind. The are prepared, bite-size or cup-size packages of compressed sugar grains.</div><div><br></div><div> --Fred</div>
</div><div> </div></div>