On Sat, 5 May 2007 09:37:17 -0400 "Stephen P. Becker" <[EMAIL PROTECTED]> wrote:
> > What experience? So far there have been no news items. The issue > > about elog messages being one shot things is rather outdated (at > > least for portage), and post-merge information is the domain of > > elog (as stated in the GLEP). > > As Ciaran explained below, the paludis overlay has been using them for > a long time, but allow me to elaborate as one who has found these news > items very useful, and who has been very unsatisfied with elog in > general. > I love getting information on news items that I can > read at my own leisure via eselect news. For example, a recent news > item in the paludis overlay informed users on how to properly set > everything up for userpriv with paludis-0.22, a description that was > far too detailed for elog, and which I didn't have time to read the > very minute that I installed the new version. What do you know...the > next day I was ready to set things up...and oh look, there was nice, > detailed instructions waiting for me to read with eselect news. Guess you never looked at the various elog modules in portage-2.1 then which provide the same (I'd say even more) flexibility how and when you want to read such stuff (the demo hook in paludis is very limited in comparison). Besides as Jakub has pointed out (and I agree with him on this for once) your example definitely belongs into the realm of upstream documentation. Do you really want to make glep 42 an RSS feed for upstream documentation? > It's easy for you and others in this thread to speculate > without *any* experience here. I really get the feeling that you guys > are talking out of your ass because this is another ciaran/paludis > thread. Why does every discussion recently have to come down to this argument? I couldn't care less wether this was about paludis, pkgcore, portage, mysql, subversion, kde, gnome, vim, emacs, apache or whatever, a g42 news item shouldn't be issued for minor syntax changes in config files that could just as well handled completely automatically in postinst/CONFIG_PROTECT. And as said above, there is the flipside that you (apparently) don't have much experience with elog (as implemented in portage) either, so that argument doesn't hold either. > As has already been pointed out, only paludis users would see > the news item that you are all bitching about, so if you guys don't > use paludis, why do you care? The point is that it sets a precedence. After all some people might be silly enough to expect the tree to be somewhat consistent when it comes to such things. There was a reason why I asked in the original discussion about glep 42 how many news items might potentially exist at any given point in time (back then the answer was "not so many"). And if there really is going to be a news item for every triviality in the tree not only will people over time become trained to ignore them but also the overhead will get quite annoying. > If you happen to maintain packages and > you feel like providing news will piss your users off, then don't > provide it. Experience has shown that paludis users like these news > items, which is another point that you and others are ignoring. (My) Experience has also shown that gentoo-x86/portage users like the elog features in portage, so stop with those games, they don't get us anywhere. Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.
signature.asc
Description: PGP signature
