Hi.<br><br>There's no way to avoid developers setting up their own repositories if they want to do it for whatever<br>reason they might have.<br>Having a "temporary repository" flag or keyword in the install file, would help as these<br>
developers could use a .install file that adds the temporary repositories, install the application,<br>then removes the repository.<br><br>Also "external" repositories or application that comes from external ones, could be colored<br>
in yellow (warning), not installable ones (AM knows that) in red and installable ones (from known<br>repositories) in green.<br>An External repository can be anything that is not from Nokia and not from Maemo.<br><br>I have my Xournal diablo alpha version in the Extras-devel since a long time now and I had many users<br>
that installed it as they found the update when another application required the extras-devel repository,<br>added it and left it there.<br><br>AM could also implement filters. Show All applications, Applications from known repositories, Applications<br>
from external repositories.<br><br>Sorry for not exposing the ideas in a better way, too late and tired. :)<br><br>Aniello<br><br><br><div class="gmail_quote">On Tue, Nov 25, 2008 at 10:16 PM, Simon Pickering <span dir="ltr"><<a href="mailto:S.G.Pickering@bath.ac.uk">S.G.Pickering@bath.ac.uk</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;"><div class="Ih2E3d"><br>
> the unstable repository--whatever, so the user decides (perhaps with<br>
> the encouragement of some of their peers) to dive in, add the unstable<br>
> repository and install the application.<br>
<br>
</div>Use an install file to install the application in question? Assuming<br>
the application needs libraries which are contained in the<br>
extras-devel repo, you'd need to temporarily enable that repo. My<br>
feeling is that the repos enabled/added as part of install files<br>
should be disabled immediately after the app in question has been<br>
added in any case, so I suggest this change is made to the way<br>
Application Manager handles the install files.<br>
<br>
Would that achieve the desired goal? It would require that a list of<br>
application install files are available (perhaps auto-generated from<br>
the contents of the repo, or perhaps by the author in question?)<br>
<div class="Ih2E3d"><br>
> packages origin (color coding, a small icon) and notices might also<br>
> help ("this package is unstable software, and may contain many<br>
> significant bugs, are you sure you want to install it?"), or even some<br>
> sort of apt pinning system to ignore certain updates.<br>
<br>
</div>I also like the idea of flagging applications that come from somewhere<br>
other than Extras, and I suppose it would be possible to have an<br>
Updates section with Stable and Unstable candidates in it (or perhaps<br>
allow updates to be sorted by their origin repo - and have Extras as<br>
the default origin). But these are still more for power users, simply<br>
disabling the repo immediately after use is imo a better bet for<br>
unskilled "users".<br>
<br>
Cheers,<br>
<font color="#888888"><br>
<br>
Simon<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
maemo-developers mailing list<br>
<a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>anidel<br>