Il giorno mer, 01/12/2010 alle 19.05 +0100, Thomas Kahle ha scritto: > > > I agree, comments within the ebuild are practically invisible to > archteams (at least to me for x86). But also running repoman is > usually > the final step, right before committing. The place for comments that > need to be considered during archtesting would be right in the stable > request bug. This is where I usually start.
This is where I usually try to provide them; it's a bit more complex when users require the stable themselves, or when new developers are replacing the old ones. > > If I do normal build tests first and then find they have been in vain > when running repoman, then I wasted cycles for the build tests. I'm > unsure if this would apply to your original example, though. > I sincerely expect(ed) a repoman scan of the ebuild to be done after tweaking keywords to ensure all the deps are stable already, thus why I asked it to be printed on scan. -- Diego Elio Pettenò — “Flameeyes” http://blog.flameeyes.eu/ If you found a .asc file in this mail and know not what it is, it's a GnuPG digital signature: http://www.gnupg.org/
