Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2009-01-16 Thread Peter Volkov
В Срд, 14/01/2009 в 20:24 -0800, Donnie Berkholz пишет:
 On 11:05 Mon 12 Jan , AllenJB wrote:
  In my opinion the cvs commit log and the ChangeLog serve 2 different  
  purposes. The cvs log is for developers while the ChangeLog is for  
  users. While the cvs log will likely just want to explain what change  
  was made, the ChangeLog should explain why it was made.
 
 So if you want to know both, you need to look in 2 places? That doesn't 
 seem very nice to me. 

We do not distribute portage tree trough cvs and rsync does not have
ChangeLog's. But even with cvs, cvs log is very slow ...

 Also in a distributed VCS, we'd want to generate 
 ChangeLogs from the commit logs

True. But portage tree is still CVS and until this happened we need
document all changes in ChangeLog's.

-- 
Peter.




Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2009-01-15 Thread Maciej Mrozowski
On Thursday 15 of January 2009 05:24:41 Donnie Berkholz wrote:

 So if you want to know both, you need to look in 2 places? That doesn't
 seem very nice to me. Also in a distributed VCS, we'd want to generate
 ChangeLogs from the commit logs to avoid all kinds of annoying conflict
 resolution and remove redundant information.

Hmm... or the other way around, so that, after making changes, echangelog 
would generate ChangeLog entry, then repoman manifest, and at the end repoman 
commit could just pick this entry and place as commit message.

It would of course make sense when all commits were 'atomic' in some way - 
(one commit per package/directory - if there's no such policy already).

-- 
regards
MM


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2009-01-14 Thread Donnie Berkholz
On 11:05 Mon 12 Jan , AllenJB wrote:
 In my opinion the cvs commit log and the ChangeLog serve 2 different  
 purposes. The cvs log is for developers while the ChangeLog is for  
 users. While the cvs log will likely just want to explain what change  
 was made, the ChangeLog should explain why it was made.

So if you want to know both, you need to look in 2 places? That doesn't 
seem very nice to me. Also in a distributed VCS, we'd want to generate 
ChangeLogs from the commit logs to avoid all kinds of annoying conflict 
resolution and remove redundant information.

 PS. I know about index2.xml - but that doesn't look like it's going to  
 be the main front page any time soon at the moment, which is a real  
 shame because it has some awesome changes.

I need to write up an announcement for the changes, then Xavier will 
flip the switch. Think days not weeks.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com


pgpEDwTiHQbg4.pgp
Description: PGP signature


Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2009-01-12 Thread Peter Volkov
В Вск, 11/01/2009 в 10:31 +0100, Benedikt Böhm пишет:
 On Sun, Jan 11, 2009 at 01:56:52AM +0100, Friedrich Oslage wrote:
  - - you forgot the ChangeLog entry
 
 `cvs log` is the changelog, i don't see why i should add a changelog entry.

There is the same reason as for ChangeLogs for ebuilds. Users (I'm user
too) don't have cvs log at hand at their systems but still consider that
it's important to know about changes.

Is it really hard to script `echangelog msg  cvs commit -m msg`?

-- 
Peter.




Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2009-01-12 Thread AllenJB

Peter Volkov wrote:

В Вск, 11/01/2009 в 10:31 +0100, Benedikt Böhm пишет:

On Sun, Jan 11, 2009 at 01:56:52AM +0100, Friedrich Oslage wrote:

- - you forgot the ChangeLog entry

`cvs log` is the changelog, i don't see why i should add a changelog entry.


There is the same reason as for ChangeLogs for ebuilds. Users (I'm user
too) don't have cvs log at hand at their systems but still consider that
it's important to know about changes.

Is it really hard to script `echangelog msg  cvs commit -m msg`?

In my opinion the cvs commit log and the ChangeLog serve 2 different 
purposes. The cvs log is for developers while the ChangeLog is for 
users. While the cvs log will likely just want to explain what change 
was made, the ChangeLog should explain why it was made.


Developers need to realise that users don't know everything about the 
software they use and don't always pin down the reasons for unexpected 
beviour. Users also don't always read the documentation given to them.


This has been seen recently in the change of default behavior of the 
world set in stable portage is a good example of this. Many users didn't 
even know about the --update option and many don't read post-commit 
messages (I expect because they don't realise the importance of those 
messages or how they can change the ELOG options to make the messages 
easier to read, for example by having them emailed to them).


There are other examples of insufficient information being given to 
users too - the dvdnav USE flag was masked recently, but neither the 
ChangeLog or the cvs commit message give any indication as to why this 
occurred.


In my opinion Gentoo developers need to do more to communicate with 
their users. This could be as simple as prominently posting 
documentation on the elog system and how to tailor it. Or it might 
involve posting more announcements to the Gentoo website (which would 
double up and make the project look more active than it currently does 
from its front page).


AllenJB

PS. I know about index2.xml - but that doesn't look like it's going to 
be the main front page any time soon at the moment, which is a real 
shame because it has some awesome changes.




Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2009-01-12 Thread Alec Warner
On Mon, Jan 12, 2009 at 3:05 AM, AllenJB gentoo-li...@allenjb.me.uk wrote:
 Peter Volkov wrote:

 В Вск, 11/01/2009 в 10:31 +0100, Benedikt Böhm пишет:

 On Sun, Jan 11, 2009 at 01:56:52AM +0100, Friedrich Oslage wrote:

 - - you forgot the ChangeLog entry

 `cvs log` is the changelog, i don't see why i should add a changelog
 entry.

 There is the same reason as for ChangeLogs for ebuilds. Users (I'm user
 too) don't have cvs log at hand at their systems but still consider that
 it's important to know about changes.

 Is it really hard to script `echangelog msg  cvs commit -m msg`?

 In my opinion the cvs commit log and the ChangeLog serve 2 different
 purposes. The cvs log is for developers while the ChangeLog is for users.
 While the cvs log will likely just want to explain what change was made, the
 ChangeLog should explain why it was made.

 Developers need to realise that users don't know everything about the
 software they use and don't always pin down the reasons for unexpected
 beviour. Users also don't always read the documentation given to them.

 This has been seen recently in the change of default behavior of the world
 set in stable portage is a good example of this. Many users didn't even know
 about the --update option and many don't read post-commit messages (I expect
 because they don't realise the importance of those messages or how they can
 change the ELOG options to make the messages easier to read, for example by
 having them emailed to them).

 There are other examples of insufficient information being given to users
 too - the dvdnav USE flag was masked recently, but neither the ChangeLog or
 the cvs commit message give any indication as to why this occurred.

 In my opinion Gentoo developers need to do more to communicate with their
 users. This could be as simple as prominently posting documentation on the
 elog system and how to tailor it. Or it might involve posting more
 announcements to the Gentoo website (which would double up and make the
 project look more active than it currently does from its front page).

It sounds like you just volunteered to write an article on elog for
the GMN...am I reading your post correctly? :)


 AllenJB

 PS. I know about index2.xml - but that doesn't look like it's going to be
 the main front page any time soon at the moment, which is a real shame
 because it has some awesome changes.




Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2008-06-23 Thread Alec Warner
2008/6/22 Peter Weller [EMAIL PROTECTED]:
 On Sun, 2008-06-22 at 15:49 +0200, Alin Nstac wrote:
 Peter Volkov wrote:
  В Сбт, 21/06/2008 в 10:56 +0200, Albert Zeyer пишет:
 
  Perhaps install a script which automatically takes the CVS comment when
  some of these files is changed and adds this comment automatically to
  the ChangeLog?
 
 
  Some days ago Diego (flameeyes) suggested to write script which will
  abort commit in case ChangeLog is not filled. Taking into account a
  number (about 1 commit per day(!)) of developers who forgive to use
  echangelog I think this is the only way to go if we want that
  ChangeLog's to be useful...
 
 
 How about fixing the right problem instead forcing devs to complete yet
 another step?
 The right way of fixing that is by creating changelogs automatically,
 based on cvs commit comments.

 Possibly by making it a part of the whole repoman commit process? I'm
 pretty sure I've mentioned this in a council meeting:
 http://www.gentoo.org/proj/en/council/meeting-logs/20080508-summary.txt
 (Check the 'New Topics' - 'When are ChangeLog entries required?'
 summary)

The portage team is always open for repoman improvements ;)


 --
 gentoo-dev@lists.gentoo.org mailing list




Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2008-06-22 Thread Peter Volkov
В Сбт, 21/06/2008 в 10:56 +0200, Albert Zeyer пишет:
 Perhaps install a script which automatically takes the CVS comment when
 some of these files is changed and adds this comment automatically to
 the ChangeLog?

Some days ago Diego (flameeyes) suggested to write script which will
abort commit in case ChangeLog is not filled. Taking into account a
number (about 1 commit per day(!)) of developers who forgive to use
echangelog I think this is the only way to go if we want that
ChangeLog's to be useful...

-- 
Peter.

-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2008-06-22 Thread Alin Năstac

Peter Volkov wrote:

В Сбт, 21/06/2008 в 10:56 +0200, Albert Zeyer пишет:
  

Perhaps install a script which automatically takes the CVS comment when
some of these files is changed and adds this comment automatically to
the ChangeLog?



Some days ago Diego (flameeyes) suggested to write script which will
abort commit in case ChangeLog is not filled. Taking into account a
number (about 1 commit per day(!)) of developers who forgive to use
echangelog I think this is the only way to go if we want that
ChangeLog's to be useful...

  
How about fixing the right problem instead forcing devs to complete yet 
another step?
The right way of fixing that is by creating changelogs automatically, 
based on cvs commit comments.





signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2008-06-22 Thread Peter Weller
On Sun, 2008-06-22 at 15:49 +0200, Alin Nstac wrote:
 Peter Volkov wrote:
  В Сбт, 21/06/2008 в 10:56 +0200, Albert Zeyer пишет:

  Perhaps install a script which automatically takes the CVS comment when
  some of these files is changed and adds this comment automatically to
  the ChangeLog?
  
 
  Some days ago Diego (flameeyes) suggested to write script which will
  abort commit in case ChangeLog is not filled. Taking into account a
  number (about 1 commit per day(!)) of developers who forgive to use
  echangelog I think this is the only way to go if we want that
  ChangeLog's to be useful...
 

 How about fixing the right problem instead forcing devs to complete yet 
 another step?
 The right way of fixing that is by creating changelogs automatically, 
 based on cvs commit comments.
 
Possibly by making it a part of the whole repoman commit process? I'm
pretty sure I've mentioned this in a council meeting:
http://www.gentoo.org/proj/en/council/meeting-logs/20080508-summary.txt
(Check the 'New Topics' - 'When are ChangeLog entries required?'
summary)

-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2008-06-21 Thread Albert Zeyer

On Sat, 2008-06-21 at 10:43 +0400, Peter Volkov wrote:
 В Чтв, 19/06/2008 в 21:03 +, Michael Sterrett (mr_bones_) пишет:
  mr_bones_08/06/19 21:03:29
  
Modified: package.mask
Log:
mask =games-kids/gcompris-8.4.5 until
http://bugs.gentoo.org/show_bug.cgi?id=225883 is fixed up.
  
  Revision  ChangesPath
  1.8740   profiles/package.mask
 
 Whenever you modify anything in profiles directory, please, fill in
 ChangeLog. ChangeLogs became useless if only part of developers fill
 them. 
 
 Just to remind. There are per-arch ChangeLog, base profile ChangeLog,
 features ChangeLog and for other stuff ChangeLog:
 
 /usr/portage/profiles/base/ChangeLog
 /usr/portage/profiles/arch/sh/ChangeLog
 [snip other archs ChangeLog]
 /usr/portage/profiles/default-bsd/ChangeLog
 /usr/portage/profiles/embedded/ChangeLog
 /usr/portage/profiles/default-linux/arm/ChangeLog
 [snip other archs ChangeLog]
 /usr/portage/profiles/hardened/x86/ChangeLog
 /usr/portage/profiles/features/ChangeLog
 /usr/portage/profiles/ChangeLog
 
 Thus whenever you change anything in arch profile, or in base or
 features subdirectory use relevant ChangeLog. For other changes like
 local USE flags documentation, masking/unmasking/updating masks (not
 comments :)) use /usr/portage/profiles/ChangeLog.

Perhaps install a script which automatically takes the CVS comment when
some of these files is changed and adds this comment automatically to
the ChangeLog?


-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2008-06-21 Thread Robin H. Johnson
On Sat, Jun 21, 2008 at 10:56:51AM +0200, Albert Zeyer wrote:
  Thus whenever you change anything in arch profile, or in base or
  features subdirectory use relevant ChangeLog. For other changes like
  local USE flags documentation, masking/unmasking/updating masks (not
  comments :)) use /usr/portage/profiles/ChangeLog.
 Perhaps install a script which automatically takes the CVS comment when
 some of these files is changed and adds this comment automatically to
 the ChangeLog?
echangelog works perfectly AFAIK.

-- 
Robin Hugh Johnson
Gentoo Linux Developer  Infra Guy
E-Mail : [EMAIL PROTECTED]
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85


pgp2Jp7D1L2Va.pgp
Description: PGP signature


Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask

2008-06-21 Thread Peter Weller
On Sat, 2008-06-21 at 11:38 -0700, Robin H. Johnson wrote:
 On Sat, Jun 21, 2008 at 10:56:51AM +0200, Albert Zeyer wrote:
   Thus whenever you change anything in arch profile, or in base or
   features subdirectory use relevant ChangeLog. For other changes like
   local USE flags documentation, masking/unmasking/updating masks (not
   comments :)) use /usr/portage/profiles/ChangeLog.
  Perhaps install a script which automatically takes the CVS comment when
  some of these files is changed and adds this comment automatically to
  the ChangeLog?
 echangelog works perfectly AFAIK.
 

I think he meant something which would add an entry to the ChangeLog
during the commit stage without extra intevention. Having said that,
many developers have some form of commit script which contains things
like manifest, changelog and commit commands.

welp

-- 
gentoo-dev@lists.gentoo.org mailing list