1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 31/10/12 12:15 PM, Samuli Suominen wrote: |
5 |
> On 31/10/12 17:39, Alexis Ballier wrote: |
6 |
>> On Wed, 31 Oct 2012 11:35:41 -0400 Ian Stakenvicius |
7 |
>> <axs@g.o> wrote: |
8 |
>> |
9 |
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 |
10 |
>>> |
11 |
>>> On 31/10/12 11:26 AM, Alexis Ballier wrote: |
12 |
>>>> On Tue, 30 Oct 2012 18:39:44 -0600 Ryan Hill |
13 |
>>>> <dirtyepic@g.o> wrote: [...] |
14 |
>>>>>> The file is pointless if not everyone is using it. I've |
15 |
>>>>>> offered to remove the file before, and I'm reoffering to |
16 |
>>>>>> do so now. |
17 |
>>>>> |
18 |
>>>>> It's pointy enough for most uses. Let's keep it that way. |
19 |
>>>> |
20 |
>>>> I would like to know what are those uses. Here are my |
21 |
>>>> thoughts about changelogs: |
22 |
>>>> |
23 |
>>>> We have cvs logs, cvsweb, etc. So what is the value added |
24 |
>>>> from changelogs? Well, those logs are per-file as far as I |
25 |
>>>> know, and since a new version of a package means a new |
26 |
>>>> .ebuild file, keeping track of changes to packages is painful |
27 |
>>>> without a changelog which is global to the whole package. |
28 |
>>>> Even if we have all the needed information in the cvs log, |
29 |
>>>> changelogs for packages are definitely useful. Now for |
30 |
>>>> eclasses the situation is different: I want to know what has |
31 |
>>>> recently changed in foo.eclass, what is the fastest way? |
32 |
>>>> Search through a changelog file with dozens of absolutely |
33 |
>>>> unrelated information, or run cvs log/go to |
34 |
>>>> sources.gentoo.org ? I tend to do the latter and find eclass |
35 |
>>>> changelogs completely useless. |
36 |
>>>> |
37 |
>>> |
38 |
>>> Cool, you do, that's great. This doesn't mean others don't use |
39 |
>>> a different process tho, and since it *IS* there and is |
40 |
>>> *SUPPOSED* to be filled, and it really doesn't hurt to run |
41 |
>>> 'echangelog "${msg}" && cvs ci -m "${msg}"' , why not do it? |
42 |
>> |
43 |
>> so that others are not encouraged to work sub-optimally :) |
44 |
>> |
45 |
> |
46 |
> eclass/ handling should go to repoman and the automated ChangeLog |
47 |
> process, should be rather straight forward for knowing person. |
48 |
> |
49 |
|
50 |
I agree, that'd make the whole thing easier. But until repoman can |
51 |
commit in eclass/ it shouldn't be that hard to just run echangelog , |
52 |
as "inefficient" as that may be. :) |
53 |
-----BEGIN PGP SIGNATURE----- |
54 |
Version: GnuPG v2.0.19 (GNU/Linux) |
55 |
|
56 |
iF4EAREIAAYFAlCRUSYACgkQ2ugaI38ACPAr7AD/ZlbMpcMm2/654o2EroXgpblD |
57 |
E+g+9ARBZxqxxDLlklQA/ivTUWlSGBXufWe/qQfzpRBvm+ms+cpCys6IMe3N7S4e |
58 |
=pwjP |
59 |
-----END PGP SIGNATURE----- |