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