| 1 |
Jason Stubbs wrote: |
| 2 |
> On Saturday 05 November 2005 03:53, Alec Joseph Warner wrote: |
| 3 |
> |
| 4 |
>>As far as including news in the tree goes, news is repository bound |
| 5 |
>>information. Each repository may in fact have relevant news, and in |
| 6 |
>>preparation for multiple repositories this is how the news should be |
| 7 |
>>handled. It goes with the rest of the repo-specific information. That |
| 8 |
>>is why it should be in the tree. |
| 9 |
> |
| 10 |
> |
| 11 |
> I seem to be repeating myself... What's an example of repository-specific |
| 12 |
> non-package-specific news? Why does `emerge --changelog` not suffice for |
| 13 |
> package-specific news? |
| 14 |
> |
| 15 |
> -- |
| 16 |
> Jason Stubbs |
| 17 |
|
| 18 |
Ok so I'm pwned there ;) |
| 19 |
|
| 20 |
emerge --changelog has no 'official' format. I believe echangelog |
| 21 |
actually puts the changes in the correct format for emerge -l to read, |
| 22 |
however not everyone uses echangelog. Many developers commit in an |
| 23 |
incompatable syntax causing the parsing to fail. This I believe, is an |
| 24 |
implementation issue. Obviously if someone is trying to get an upgrade |
| 25 |
guide to users they aren't going to commit in an incompatable format. |
| 26 |
|
| 27 |
We had a similar discussion before and many people wanted gentoo |
| 28 |
changelogs to stay true to only gentoo changes, thus some think a gentoo |
| 29 |
changelog is an inappropriate place to look for upgrade guides and |
| 30 |
errata. Changelogs are also not easy to search through and the current |
| 31 |
syntax does not provide all the benifits of the syntax provided by GLEP 42. |
| 32 |
|
| 33 |
So the options for using emerge --changelog are basically, updating the |
| 34 |
syntax to make it useful, probably audit the changelog code in emerge to |
| 35 |
make sure it works better ( even half decent 'entries' aren't grabbed, |
| 36 |
but I haven't looked at the changelog code in months ). This of course |
| 37 |
makes emerge the newsreader you didn't want, although I'm sure the |
| 38 |
eselect module could be modified to read Changelog's just as easily. |
| 39 |
|
| 40 |
Also, nothing covers the expiration of Changelog contents vs expiration |
| 41 |
of news items, since the news items are file independent, what if a |
| 42 |
bunch of commits basically erases a relevant news item out of the changelog? |
| 43 |
|
| 44 |
Certainly I would support either way ( news or changelog ) although in |
| 45 |
the latter case there are some seperate issues that need to be worked |
| 46 |
out ( mostly policy issues ). |
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives