On Fri, 1 Feb 2019 at 03:26, Nicolas Mailhot <nicolas.mailhot@laposte.net> wrote:
Le jeudi 31 janvier 2019 à 19:52 -0500, Neal Gompa a écrit :
> On Thu, Jan 31, 2019 at 6:58 PM Stephen John Smoogen <smooge@gmail.com
> > wrote:
> > On Thu, 31 Jan 2019 at 07:28, Igor Gnatenko <
> > ignatenkobrain@fedoraproject.org> wrote:
> > > Problem №1: Build-only packages
> > >
> > > Rawhide gating makes this much more complicated because builds
> > > appear in buildroot slower, updating group of packages would need
> > > side tags and it’s just painful to work with.
> > >
> > > https://pagure.io/fesco/issue/2068
> > >
> > > And, after all, those packages shouldn’t be shipped to users.
> >
> > My main problem with this is the above. Yes Joe Desktop User isn't
> > going to see/need that package.. but we have a LOT of packagers who
> > take our stuff and rebuild it for themselves for various reasons. I
> > find it hard to put together the proposal which is supposed to make
> > developing/packaging easier with making developing/packaging harder.
> > Whether you want it to or not, this comes across as "If you want to
> > use Go or Rust, you will need our special set of tools which we keep
> > hidden."
> >
>
> This is actually something I really don't like either. But the Fedora
> leadership has pushed very hard on the concept of having packages that
> aren't available to "normies", and require special tooling to be able
> to leverage (that for various reasons, I can't even use as a third
> party packager!).

If MBI is about hiding build packages I don't see the point and I'm not
interested.


Actually I don't think it is part of MBI but comes up in some Rust/Go packages which do regular chain-bootstrapping to be bleeding edge. I will let someone more versed in it speak on the specifics as I usually see red on hidden packages and am not a disinterested party.
 



--
Stephen J Smoogen.