On Tue, Feb 20, 2018 at 3:51 PM, Geraldo Netto <[email protected]> wrote:
> Hello Waldek/Nadav/All, > > Totally agreed Waldek! > And maybe we could also define a policy to phase out apps that are not > maintained for a long time > eg: let's suppose we have an apps that is not updated for more than 3 years > we do a survey in the mailing list, then, if no one is using, we remove it > from apps > One of the ideas of the "apps" repository is that it is tiny - it doesn't include any big tarballs or anything (it gets those from the Internet), just build scripts. So the unmaintained packages don't really incur any big cost. But you're right that they are annoying because it makes it seems like something should work, but it doesn't. One thing we could do is to create a subdirectory in apps, "broken/" and moved broken packages there after a (say) week that nobody expresses any interest to fix them. This way, it is trivial to move such an application back to the main directory if someone gains interest in them and cares to unbreak them. > > Also, is there any all to modularise the apps and the external > directories? > I'm asking this, because I have no interesting in many apps and yet, I have > to download the whole apps > The apps repository is tiny, about 2 MB. It just contains scripts. I don't see any problem downloading the "whole" of it :-) But, > As for the external, I don't use the ARM 64 (aarch64 if I got it right), > so, for my case, it's totally useless > you're right about "external". It's big, and also the need for much of it is dubious. See https://github.com/cloudius-systems/osv/issues/743 for my suggestion on removing most of it. -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
