Re: [gentoo-dev] Please use eselect news items!

2009-06-27 Thread Ulrich Mueller
 On Fri, 26 Jun 2009, Dale wrote:

 I would like to see what you guys think about a small feature. Is
 there a way to put a number next to each item and then we can select
 by the number instead of typing the LONG name for the item? Sort of
 like gcc-config -l does its listing and you can set with the
 appropriate number.

 This would save time and some typing and seems like something that
 would be fairly easy to do.

Already done. ;-) Try eselect news-tng that comes with =eselect-1.1.

Ulrich



Re: [gentoo-dev] Please use eselect news items!

2009-06-27 Thread Dale
Ulrich Mueller wrote:
 On Fri, 26 Jun 2009, Dale wrote:
 

   
 I would like to see what you guys think about a small feature. Is
 there a way to put a number next to each item and then we can select
 by the number instead of typing the LONG name for the item? Sort of
 like gcc-config -l does its listing and you can set with the
 appropriate number.
 

   
 This would save time and some typing and seems like something that
 would be fairly easy to do.
 

 Already done. ;-) Try eselect news-tng that comes with =eselect-1.1.

 Ulrich


   

Dang.  No wonder I am so poor.  I always come up with something that is
already done.  THAT little feature is so cool.  Now to remember it.  :/

Thanks. 

Dale

:-)  :-)





Re: [gentoo-dev] Please use eselect news items!

2009-06-26 Thread Ben de Groot
AllenJB wrote:
 As a user, I'd like to encourage developers to make use of news items
 (eselect news) for important changes. 

 2 recent changes I would suggest having news items for are the libpcre
 .la files issue, because it often doesn't get noticed until later when
 builds fail, and the masking of the kdeprefix use flag as this is a
 fairly major change and I think it's useful for users to know why these
 changes are being made.

I wholeheartedly agree. Such fairly invasive changes should be brought
to the attention of our users by the best means available, which
certainly includes the eselect news method. I am of the opinion it was a
fairly serious failure not to do so in both cases Allen mentioned.

Please think of the users and inform them!

Cheers,
Ben



Re: [gentoo-dev] Please use eselect news items!

2009-06-26 Thread Fabian Groffen
On 25-06-2009 22:57:08 +0100, AllenJB wrote:
 As a user, I'd like to encourage developers to make use of news items 
 (eselect news) for important changes. I find them much more noticeable 
 than elog messages (which, while I have set them up so they get emailed 
 to me, I admit I don't always read). I think they're also easier to go 
 back and re-read later (not everyone knows how to dig out old elog 
 messages).

Maybe we should make an option to have portage not notice you of new
news messages until you have read it to make the feature more popular.

I personally felt after the java-config news message that it's more of a
bugger than a help, since I have many systems, and on all of them I had
to read it to get rid of the waiting news message.

And no, excluding them in the rsync sync is not the option, as I want to
be able to read them if I don't recall the details any more...


just my 2 cents why I am avoiding adding news messages these days


-- 
Fabian Groffen
Gentoo on a different level



Re: [gentoo-dev] Please use eselect news items!

2009-06-26 Thread Zac Medico
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Fabian Groffen wrote:
 On 25-06-2009 22:57:08 +0100, AllenJB wrote:
 As a user, I'd like to encourage developers to make use of news items 
 (eselect news) for important changes. I find them much more noticeable 
 than elog messages (which, while I have set them up so they get emailed 
 to me, I admit I don't always read). I think they're also easier to go 
 back and re-read later (not everyone knows how to dig out old elog 
 messages).
 
 Maybe we should make an option to have portage not notice you of new
 news messages until you have read it to make the feature more popular.

Seem like that will mostly defeat the purpose since you'll probably
forget you set that option and then miss future news items. Shrug,
we can do it if there's demand for it though.

- --
Thanks,
Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkpFIS8ACgkQ/ejvha5XGaMvGQCfT3ISYyNwD6woPA7DdSO82P4P
jRUAn18+6QVcVyroCgOS/5UboiVgE+Te
=Ph9j
-END PGP SIGNATURE-



Re: [gentoo-dev] Please use eselect news items!

2009-06-26 Thread Alec Warner
On Fri, Jun 26, 2009 at 11:25 AM, Fabian Groffengrob...@gentoo.org wrote:
 On 25-06-2009 22:57:08 +0100, AllenJB wrote:
 As a user, I'd like to encourage developers to make use of news items
 (eselect news) for important changes. I find them much more noticeable
 than elog messages (which, while I have set them up so they get emailed
 to me, I admit I don't always read). I think they're also easier to go
 back and re-read later (not everyone knows how to dig out old elog
 messages).

 Maybe we should make an option to have portage not notice you of new
 news messages until you have read it to make the feature more popular.

 I personally felt after the java-config news message that it's more of a
 bugger than a help, since I have many systems, and on all of them I had
 to read it to get rid of the waiting news message.

Well that how it was designed ;)

But seriously if you have N machines of the same config; it would make
sense to just turn off or ignore notifications on N-1 machines and
just always read news on one machine (maybe the canary machine).  But
if they all have different configs and installed packages; turning off
notifications could be dangerous ;)

-A


 And no, excluding them in the rsync sync is not the option, as I want to
 be able to read them if I don't recall the details any more...


 just my 2 cents why I am avoiding adding news messages these days


 --
 Fabian Groffen
 Gentoo on a different level





Re: [gentoo-dev] Please use eselect news items!

2009-06-26 Thread Dale
AllenJB wrote:
 Hi all,

 As a user, I'd like to encourage developers to make use of news items
 (eselect news) for important changes. I find them much more noticeable
 than elog messages (which, while I have set them up so they get
 emailed to me, I admit I don't always read). I think they're also
 easier to go back and re-read later (not everyone knows how to dig out
 old elog messages).

 2 recent changes I would suggest having news items for are the libpcre
 .la files issue, because it often doesn't get noticed until later when
 builds fail, and the masking of the kdeprefix use flag as this is a
 fairly major change and I think it's useful for users to know why
 these changes are being made.

 Another case is that prior to it's masking, the kdeprefix use flag
 was deprecated, with only an elog message on every kde package to
 notify users, resulting in users who have their elog messages emailed
 to them receiving a very large number of emails all with the same
 content - I would also suggest news items in such cases in future.


 Thanks to all the developers who worked to bring us this long awaited
 feature - I think it's brilliant, so please use it!

 AllenJB




I would like to see what you guys think about a small feature.  Is there
a way to put a number next to each item and then we can select by the
number instead of typing the LONG name for the item?  Sort of like
gcc-config -l does its listing and you can set with the appropriate number.

This would save time and some typing and seems like something that would
be fairly easy to do. 

Dale

:-)  :-) 



[gentoo-dev] Please use eselect news items!

2009-06-25 Thread AllenJB

Hi all,

As a user, I'd like to encourage developers to make use of news items 
(eselect news) for important changes. I find them much more noticeable 
than elog messages (which, while I have set them up so they get emailed 
to me, I admit I don't always read). I think they're also easier to go 
back and re-read later (not everyone knows how to dig out old elog 
messages).


2 recent changes I would suggest having news items for are the libpcre 
.la files issue, because it often doesn't get noticed until later when 
builds fail, and the masking of the kdeprefix use flag as this is a 
fairly major change and I think it's useful for users to know why these 
changes are being made.


Another case is that prior to it's masking, the kdeprefix use flag was 
deprecated, with only an elog message on every kde package to notify 
users, resulting in users who have their elog messages emailed to them 
receiving a very large number of emails all with the same content - I 
would also suggest news items in such cases in future.



Thanks to all the developers who worked to bring us this long awaited 
feature - I think it's brilliant, so please use it!


AllenJB