On Thu, Jan 24, 2013 at 01:06:21PM +0100, Vít Ondruch wrote: > Dne 24.1.2013 11:22, Richard W.M. Jones napsal(a): > >The flip side of this is that when you *don't* build in Rawhide you > >potentially push work and breakage to somebody else. Your package may > >not build in Rawhide, leaving someone else to find that out when they > >try to rebuild it or do a mass rebuild. And inheritance sometimes > >doesn't work or does something unexpected, and others have to pick up > >the pieces. > > It definitely depends on package. I should be the one who knows > about my packages the best if there is some breaking potential. In the sense that it's better for the maintainer to fix the Rawhide build rather than someone else much later on, I think we agree. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
