Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask
В Вск, 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
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
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.
[gentoo-dev] Anouncement: Updated kde4 eclasses in the tree.
Hi,
we gentoo kde devs and our herd testers would like to anounce that we have
prepared new kde4 eclasses which supports working with more kdes and has many
many features.
I will try to give you some info about usage and so on.
So first let take look under the hood (supported stuff):
* koffice2 (with these eclasses you can build reasonably split koffice stuff
:])
* linguas support (you have to install only languages user want)
* live ebuilds support (we support by default usage of subversion ebuilds
directly so you inherit the same eclass)
* reworked dependency blocks (so your application will work with kde-4.1
kde-4.2 or with every version, it is your call :])
* only EAPI=2 (this you might not like but every ebuild inheriting our
eclasses needs to be eapi2, sorry guys it is much simpler and cleaner)
* syntax cleanup (we polished the eclass so it should be readable for most
people and it should be easy to spot and fix error).
So what changes for you developers wanting to write some stuff:
1) new variables (all must be before inherit of our nice eclass)
KDE_LINGUAS=cs s...@latn uk # for specifying linguas in the package (These
must be all specified! so if you have some .po .ts and others in your package
you should fix up!)
NEED_KDE=4.3 # this variable is used for specifying dependency on certain
kde version, you should not define this variable if you are not sure, we have
nice fallback.
KDE_MINIMAL=4.3 # aproximate minimal needed kde version for your package.
Can be used as DEPEND==kde-base/libkonq-${KDE_MINIMAL}[kdeprefix=].
KDE_WANTED=4.2 # this is internal variable used for specifying deps search
order. If user has kdeprefix we start version search from this version so it
gets first if installed or pulled. (really usefull only for internal kde use).
2) as example ebuilds you can browse kde-testing [1] and kde-crazy [2]
3) we also open new ~6months long oportunity window for feature call and code
cleanups :P
Enjoy using the new eclass :]
Tomas
PS: I really hope i didnt miss something important.
PPS: I really really hope that this time kmail will sent this as only text
mail not html one.
[1] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=summary
[2] http://git.overlays.gentoo.org/gitweb/?p=proj/kde-crazy.git;a=summary
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-dev] Anouncement: Updated kde4 eclasses in the tree.
Tomáš Chvátal wrote: Hi, SNIP Tomas PS: I really hope i didnt miss something important. PPS: I really really hope that this time kmail will sent this as only text mail not html one. And in the future, hit compose new message instead. Your message appears as part of a thread of the subject: Automated Package Removal and Addition Tracker, for the week ending 2009-01-11 23h59 UTC That could mean some won't see your post. I almost didn't myself. I was curious since no one replies to that automated thing. Who would answer if they did? :/ Dale :-) :-)
Re: [gentoo-dev] Anouncement: Updated kde4 eclasses in the tree.
Well that is the problem, I didnt hit reply but new message button :D (i guess kmail4.2 is doing something fancy :D) Tomas signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Anouncement: Updated kde4 eclasses in the tree.
Tomáš Chvátal wrote: Well that is the problem, I didnt hit reply but new message button :D (i guess kmail4.2 is doing something fancy :D) Tomas Yep, time to search the configure section. Something windoze like going on in there. lol Dale :-) :-)
Re: [gentoo-dev] Anouncement: Updated kde4 eclasses in the tree.
On Mon, Jan 12, 2009 at 2:00 PM, Dale rdalek1...@gmail.com wrote: Tomáš Chvátal wrote: Hi, SNIP Tomas PS: I really hope i didnt miss something important. PPS: I really really hope that this time kmail will sent this as only text mail not html one. And in the future, hit compose new message instead. Your message appears as part of a thread of the subject: Automated Package Removal and Addition Tracker, for the week ending 2009-01-11 23h59 UTC That could mean some won't see your post. I almost didn't myself. I was curious since no one replies to that automated thing. Who would answer if they did? :/ his original message contained: References: e1lmasl-0002kk...@stork.gentoo.org In-Reply-To: e1lmasl-0002kk...@stork.gentoo.org Which I assume confused a subset[1] of clients because that messageID is from Robin's automated message. I dunno why kmail would do such a thing if you claim to have written a new message though; maybe some testing is in order ;) -Alec [1] gmail apparently ignores said headers and figures out what is a 'conversation' some other way. Dale :-) :-)
