| 1 |
AllenJB wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> As a user, I'd like to encourage developers to make use of news items |
| 5 |
> (eselect news) for important changes. I find them much more noticeable |
| 6 |
> than elog messages (which, while I have set them up so they get |
| 7 |
> emailed to me, I admit I don't always read). I think they're also |
| 8 |
> easier to go back and re-read later (not everyone knows how to dig out |
| 9 |
> old elog messages). |
| 10 |
> |
| 11 |
> 2 recent changes I would suggest having news items for are the libpcre |
| 12 |
> .la files issue, because it often doesn't get noticed until later when |
| 13 |
> builds fail, and the masking of the "kdeprefix" use flag as this is a |
| 14 |
> fairly major change and I think it's useful for users to know why |
| 15 |
> these changes are being made. |
| 16 |
> |
| 17 |
> Another case is that prior to it's masking, the "kdeprefix" use flag |
| 18 |
> was deprecated, with only an elog message on every kde package to |
| 19 |
> notify users, resulting in users who have their elog messages emailed |
| 20 |
> to them receiving a very large number of emails all with the same |
| 21 |
> content - I would also suggest news items in such cases in future. |
| 22 |
> |
| 23 |
> |
| 24 |
> Thanks to all the developers who worked to bring us this long awaited |
| 25 |
> feature - I think it's brilliant, so please use it! |
| 26 |
> |
| 27 |
> AllenJB |
| 28 |
> |
| 29 |
> |
| 30 |
|
| 31 |
|
| 32 |
I would like to see what you guys think about a small feature. Is there |
| 33 |
a way to put a number next to each item and then we can select by the |
| 34 |
number instead of typing the LONG name for the item? Sort of like |
| 35 |
gcc-config -l does its listing and you can set with the appropriate number. |
| 36 |
|
| 37 |
This would save time and some typing and seems like something that would |
| 38 |
be fairly easy to do. |
| 39 |
|
| 40 |
Dale |
| 41 |
|
| 42 |
:-) :-) |
Archives