Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

[Michał Górny]

On Thu, 16 Jun 2016 09:40:53 -0500
james <garftd@×××××××.net> wrote:

> On 06/16/2016 10:04 AM, Michał Górny wrote:
> > On Thu, 16 Jun 2016 08:59:44 -0500
> > james <garftd@×××××××.net> wrote:
> >
> >> On 06/16/2016 02:51 AM, Alexander Berntsen wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA512
> >>>
> >>> On 16/06/16 09:39, Daniel Campbell wrote:
> >>>> I guess what I mean is these outside developers could continue
> >>>> hacking and/or breaking things, or whatever else, without worrying
> >>>> about their "official" branch. We could have a standard that
> >>>> assumes Gentoo pulls their 'master' branch and they keep other
> >>>> stuff in 'dev', or some other model. We'll need to decide on *some*
> >>>> branch, but putting it in writing would make things clearer for
> >>>> prospective repo maintainers.
> >>
> >>> OK, then I think that it would be a good idea to have a gentoo-ci
> >>> branch, or similar, if the assumption is merely that this is where
> >>> Gentoo developers will look when evaluating your repository.
> >>>
> >> Ok, if we go this route, here is a basic simple question. Why can't the
> >> "gentoo-ci" be a package, or group of packages that runs in a private
> >> persons own resources, regardless it is a single gentoo server or a
> >> small cluster (openstack)? That way, those gentoo-ciruns can be
> >> performed by the proxy or the author thus reducing the workload for QA
> >> or other devs.  I guess what I'm really asking is/will the gentoo-ci be
> >> packaged up for the gentoo community to use, on a small set of packages?
> >
> > dev-util/pkgcheck is the QA tool used (you want -9999).
> >
> > https://github.com/gentoo/travis-repo-checks is the wrapper that is
> > used to run it in parallel. A lot of hackery, and master is outdated
> > for -9999. No time to fix it. The repo-mirror-ci branch is better but
> > then, I updated it recently for some local hacks.
> >
> > https://bitbucket.org/mgorny/pkgcheck-result-parser is the thingie used
> > to turn pkgcheck XML reports into pretty HTML. Also a bit hacky,
> > especially with the error & warning lists hardcoded.
> >
> > https://bitbucket.org/mgorny/repo-mirror-ci all the extra scriptery
> > used to run it all. No time to clean it up more than I already did.
> >
>
> EXCELLENT !  I seem to be mostly interested in orphaned, broken and
> controversial packages these days....not sure if that is a good thing or
> not.
>
> Do these ci tools work on gentoo snaps? [1]

I have no clue. And I doubt I'll be interested in testing that thing.

> [1]
> http://arstechnica.com/information-technology/2016/06/goodbye-apt-and-yum-ubuntus-snap-apps-are-coming-to-distros-everywhere/

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>