On Mon, Aug 30, 2010 at 11:11:06PM +0200, Miloslav Trmač wrote:
A typical developer wants the dependencies of the software they are
working on to be _very_ up to date - probably not the upstream
development version, but the upstream maintenance version with _all_
current bug fixes. Waiting 6
Matthew Miller píše v Po 30. 08. 2010 v 18:56 -0400:
On Mon, Aug 30, 2010 at 11:11:06PM +0200, Miloslav Trmač wrote:
A typical developer wants the dependencies of the software they are
working on to be _very_ up to date - probably not the upstream
development version, but the upstream
On Mon, Aug 30, 2010 at 15:56, Matthew Miller mat...@mattdm.org wrote:
On Mon, Aug 30, 2010 at 11:11:06PM +0200, Miloslav Trmač wrote:
A typical developer wants the dependencies of the software they are
working on to be _very_ up to date - probably not the upstream
development version, but
On Tue, Aug 31, 2010 at 01:05:34AM +0200, Miloslav Trmač wrote:
No, for rawhide to really be useful, it must be possible to put
unfinished system-wide changes in there: it would be pretty much
impossible to integrate systemd into the distribution on a branch, and
to add it into rawhide only
On Mon, Aug 30, 2010 at 04:30:44PM -0700, darrell pfeifer wrote:
I've moved from being a rawhide junkie to a koji junkie. I've been in that
mode for the last five or six years. My experience has been that rawhide is
most unstable just around alpha time.
That is no longer the case. See:
On Mon, 2010-08-30 at 19:52 -0400, Matthew Miller wrote:
On Mon, Aug 30, 2010 at 04:30:44PM -0700, darrell pfeifer wrote:
I've moved from being a rawhide junkie to a koji junkie. I've been in that
mode for the last five or six years. My experience has been that rawhide is
most unstable just
