On 2012-09-18 1:18 PM, Benjamin Henrion wrote: > On Tue, Sep 18, 2012 at 12:48 PM, Felix Fietkau <[email protected]> wrote: >> On 2012-09-05 1:23 PM, [email protected] wrote: >>> Hi >>> >>> I've just read the "Attitude Adjustment beta announcement" and it's not >>> clear how packages will work in the future. >>> >>> There will be "maintained and unmaintained" packages, so how will >>> maintained packages will be elected? >>> Will all packages move in the unmaintained repo waiting for a maintainer? >> Unmaintained packages will stay where they are. Maintained packages will >> be moved to trunk or (for bigger less common package groups) different >> feeds. >> >>> Will every packages need an "external" (not in the openwrt team) maintainer? >> We will only keep packages in trunk that have a maintainer (either >> member of the openwrt team or external). >> >>> About the unmaintained repo, will it be /dev/null, or a repo where there >>> will be only "compile test"? >> Unmaintained packages will not be included in binary builds, and >> developers will typically not compile-test them. >> >>> and if a "maintained or unmaintained" dependency update break a >>> "unmaintained" package Openwrt team will not do anything. >> Right. Dealing with the large number of packages pushes a big burden >> onto our small group of developers. We've decided that we can do a much >> better job of maintaining the core if we don't have to care about a big >> repository of packages with potentially only very few users. >> >>> It may be a good idea to gather some statistics (opt-in or opt-out) so you >>> can focus on the right packages >>> -an uid >>> -device info (model, rev ...) >>> -opkg list-installed >>> -... >> We will focus on the packages that we care about. If a frequently used >> package is not among that list, somebody needs to step up and start >> maintaining it. >> >>> Another idea for the unmaintained packages, github and his >>> https://github.com/blog/843-the-merge-button, this could be time saving >>> (never use) >> I agree. This does not have to be done by the core team though. Maybe a >> group of active users/contributors could organize to maintain something >> like this. If done properly, we could then include that in the default >> feeds.conf. > > It should be like gentoo overlays, anyone can easily add his own > overlay, including the hosting for the packages: > > http://www.gentoo.org/proj/en/overlays/userguide.xml We already have an easy way for people to add their own packages. feeds.conf + scripts/feeds. Repositories can be hosted anywhere.
> Or you might also think about a build farm like Ubuntu PPA, which > provides basic package binaries generation and hosting, being on the > side of the distro. > > PPA is something the debian guys never got for example. The community for OpenWrt packages is rather small compared to a general purpose distro like Ubuntu. I think we should encourage people to work together on having fewer repositories that people need to go through to find useful packages. Our snapshot and release builds already take up quite a bit of time, I'm not really fond of wasting those cycles on low-quality unmaintained packages. - Felix _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
