[gentoo-dev] Re: [news-item] Paludis 0.24
Ciaran McCreesh <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sat, 05 May 2007 00:17:46 +0100: > On Fri, 04 May 2007 17:38:43 -0500 > Steev Klimaszewski <[EMAIL PROTECTED]> wrote: >> Right which... seems to me something I would want to know *BEFORE* >> I upgraded... > > No no, if you find out before you upgrade you preemptively change your > config files and the old version breaks. If you find out after you > upgrade you know why you're getting a load of warnings about '*' being > deprecated. I believe that last word, deprecated, is what many are missing. If the files are upgraded to the new format previous to merging the new version, things will break. If the new version is installed and the files remain in the old format, it will simply spit warnings but it'll still work. Thus, switching the format must be done after the upgrade, not before, and the news message suggesting it should be shown after the upgrade, not before, to prevent breakage while explaining warnings people will get until they update to current format. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] prep* functions in ebuilds
On Friday 04 May 2007, Ciaran McCreesh wrote: > Torsten Veller <[EMAIL PROTECTED]> wrote: > > What is with prepalldocs? Is it allowed to use in ebuilds? Should it > > be in pms? Or is it just missing in prepall? > > The prep* functions are Portage internals. They're not suitable for > ebuild use and shouldn't be in pms. incorrect ... prepalldocs is meant for ebuild use -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] [news-item] Paludis 0.24
On Fri, 4 May 2007 20:01:58 -0400 Dan Meltzer <[EMAIL PROTECTED]> wrote: > > Doesn't help. It's only there once, and it's easy to ignore. Users > > don't have to explicitly mark it as read, so it's frequently not > > read. elog is not an adequate solution. > > Emm, That would depend upon the viewer I'd think. Which is kind of the point... -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
On Friday 04 May 2007 8:01:58 pm Dan Meltzer wrote: > On Friday 04 May 2007 7:52:46 pm Ciaran McCreesh wrote: > > On Fri, 4 May 2007 19:48:19 -0400 > > > > Dan Meltzer <[EMAIL PROTECTED]> wrote: > > > That seems like a really bad road to go down. > > > > > > Would it not be better to extend elog to alert people at the end of > > > an install as well? > > > > Doesn't help. It's only there once, and it's easy to ignore. Users > > don't have to explicitly mark it as read, so it's frequently not read. > > elog is not an adequate solution. > > Emm, That would depend upon the viewer I'd think. elogs are saved in a > directory, and so the only way they would disappear is if the user chose to > delete them (or the viewer did it for them). Ooops, I guess they are only saved if it's explicity enabled, there goes that idea :/ > > > > When I think of news I think of things that are > > > required to do or my system will break. That is what I want out of > > > news. I can't see how deprecated syntax fits that defination. The > > > program should warn when it finds deprecated syntax, and the users > > > will then know. Or if the users ignore it, then when the support is > > > removed and the package errors, the user fixes it then without any > > > major headache. It sure isn't something that will break a users > > > system utterly if its not acted upon. > > > > It's something that is of sufficient interest to those who will read > > the news item that a news item is warranted. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] [news-item] Paludis 0.24
On Friday 04 May 2007 7:52:46 pm Ciaran McCreesh wrote: > On Fri, 4 May 2007 19:48:19 -0400 > > Dan Meltzer <[EMAIL PROTECTED]> wrote: > > That seems like a really bad road to go down. > > > > Would it not be better to extend elog to alert people at the end of > > an install as well? > > Doesn't help. It's only there once, and it's easy to ignore. Users > don't have to explicitly mark it as read, so it's frequently not read. > elog is not an adequate solution. Emm, That would depend upon the viewer I'd think. elogs are saved in a directory, and so the only way they would disappear is if the user chose to delete them (or the viewer did it for them). > > > When I think of news I think of things that are > > required to do or my system will break. That is what I want out of > > news. I can't see how deprecated syntax fits that defination. The > > program should warn when it finds deprecated syntax, and the users > > will then know. Or if the users ignore it, then when the support is > > removed and the package errors, the user fixes it then without any > > major headache. It sure isn't something that will break a users > > system utterly if its not acted upon. > > It's something that is of sufficient interest to those who will read > the news item that a news item is warranted. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] [news-item] Paludis 0.24
On Fri, 4 May 2007 19:48:19 -0400 Dan Meltzer <[EMAIL PROTECTED]> wrote: > That seems like a really bad road to go down. > > Would it not be better to extend elog to alert people at the end of > an install as well? Doesn't help. It's only there once, and it's easy to ignore. Users don't have to explicitly mark it as read, so it's frequently not read. elog is not an adequate solution. > When I think of news I think of things that are > required to do or my system will break. That is what I want out of > news. I can't see how deprecated syntax fits that defination. The > program should warn when it finds deprecated syntax, and the users > will then know. Or if the users ignore it, then when the support is > removed and the package errors, the user fixes it then without any > major headache. It sure isn't something that will break a users > system utterly if its not acted upon. It's something that is of sufficient interest to those who will read the news item that a news item is warranted. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
On Friday 04 May 2007 6:58:44 pm Ciaran McCreesh wrote: > On Fri, 4 May 2007 18:50:00 -0400 > > Dan Meltzer <[EMAIL PROTECTED]> wrote: > > How does this fit the following parts of the GLEP? > > > > "Preemptive > > Preemptiveness is not a requirement for this particular news item. It's > necessary in many places but not this one. > > > Additionally, what about this is so critical that it will not allow > > elog to be used? > > Experience with other repositories has shown that if it's in elog, many > people won't see or read it, whereas if it's in a news item they will. > Placing it in a news item will significantly reduce the upstream > support load. That seems like a really bad road to go down. Would it not be better to extend elog to alert people at the end of an install as well? When I think of news I think of things that are required to do or my system will break. That is what I want out of news. I can't see how deprecated syntax fits that defination. The program should warn when it finds deprecated syntax, and the users will then know. Or if the users ignore it, then when the support is removed and the package errors, the user fixes it then without any major headache. It sure isn't something that will break a users system utterly if its not acted upon. -- [EMAIL PROTECTED] mailing list
[gentoo-dev] Re: [Last Rites] app-pda/plucker
Ryan Hill wrote: > # Ryan Hill <[EMAIL PROTECTED]> (29 Apr 2007) > # Has a hard dependency on wxGTK-2.4 (bug #121818) > # Replacement: sunrise? http://sourceforge.net/projects/sunrisexp/ > # Masked for removal May 29, 2007 > app-pda/plucker plucker will not be removed but will stay masked until it can play nice with wxGTK-2.6. -- where to now? if i had to guess dirtyepic gentoo orgi'm afraid to say antarctica's next 9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8) -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] [news-item] Paludis 0.24
On Sat, 05 May 2007 01:47:07 +0300 Petteri Räty <[EMAIL PROTECTED]> wrote: > How can there be new messages with emerge --pretend if emerge --sync > is the only way to get them? Should be saying unread messages and it > would be clear to me. A new message is one that hasn't been read. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
On Fri, 04 May 2007 17:38:43 -0500 Steev Klimaszewski <[EMAIL PROTECTED]> wrote: > Right which... seems to me something I would want to know > *BEFORE* I upgraded... No no, if you find out before you upgrade you preemptively change your config files and the old version breaks. If you find out after you upgrade you know why you're getting a load of warnings about '*' being deprecated. > otherwise, yeah, elog does the same thing already... Experience has shown that news items work in delivering this kind of information to users whereas elog doesn't. elog is a one-shot thing that may or may not (usually the latter) actually get seen, whereas a news item stays around until the user reads it. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Færøy wrote: > On Sat, May 05, 2007 at 12:13:12AM +0200, Vlastimil Babka wrote: >> Isn't such use case just a replacement for elog? I thought news were >> supposed to be delivered before upgrading. Also "You should update your >> configuration files after upgrading." sounds like something one would >> read before upgrade... > > It'll only affect users after they upgrade. > Right which... seems to me something I would want to know *BEFORE* I upgraded... otherwise, yeah, elog does the same thing already... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGO7Xz1c+EtXTHkJcRAgPkAKCHU2QU+nFr3l+4kteNWD4mcVQ7swCfUy76 kEoMuymvLn9+kMtI7jUxnUo= =1JPW -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] [news-item] Paludis 0.24
On Sat, 05 May 2007 00:56:35 +0200 Vlastimil Babka <[EMAIL PROTECTED]> wrote: > Display-If-Installed: signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
On Fri, 4 May 2007 18:50:00 -0400 Dan Meltzer <[EMAIL PROTECTED]> wrote: > How does this fit the following parts of the GLEP? > > "Preemptive Preemptiveness is not a requirement for this particular news item. It's necessary in many places but not this one. > Additionally, what about this is so critical that it will not allow > elog to be used? Experience with other repositories has shown that if it's in elog, many people won't see or read it, whereas if it's in a news item they will. Placing it in a news item will significantly reduce the upstream support load. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ciaran McCreesh wrote: > On Sat, 05 May 2007 01:30:05 +0300 > Petteri Räty <[EMAIL PROTECTED]> wrote: >> So let's say this was a message about package foobar. If it only >> affects users after they upgrade it would mean that new installs >> would get the news item too, wouldn't it?. > > Yep. This situation was discussed when designing GLEP 42. There isn't a > better alternative because there's no reliable record of packages that > used to be installed. Display-If-Installed: =0.24. How likely is that someone has had such version previously, then uninstalled paludis completely leaving config files around, and now installs >=0.24? So likely it's worth that future fresh installs of say 0.50 will display this news too? - -- Vlastimil Babka (Caster) Gentoo/Java -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGO7oitbrAj05h3oQRAtshAKCCJeVQ2ksDuIvX8eLGjZsxAlDxFACeNea1 Iep1M7QGhWnSfHP4drZg3rw= =nabr -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
On Fri, 4 May 2007 14:37:21 -0500 "Karl Haines" <[EMAIL PROTECTED]> wrote: > Lol, its funny that we must concern ourselves with the needs of > ""el1te gam3rs"", but I suppose its necessary. We concern ourselves with the needs of everyone, from our elite users, to our crapola devs. There are, or should, be no favourites. Hi Mom :D Roy -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] [news-item] Paludis 0.24
On Friday 04 May 2007 4:49:47 pm Piotr Jaroszyński wrote: > Hello, > > Thanks to zmedico we now have support for news items on infra-side and heck > they are ready to use. And we should use them! > > Attaching news item for paludis 0.24. > Justification: major config format change. How does this fit the following parts of the GLEP? "Preemptive Users should be told of changes before they break a system, not after the damage has already been done. Ideally, the system administrator would be given ample warning to plan difficult upgrades and changes, rather than only being told just before action is necessary." "A more reliable way of getting news of critical updates" Additionally, what about this is so critical that it will not allow elog to be used? -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] [news-item] Paludis 0.24
Ciaran McCreesh kirjoitti: > On Sat, 05 May 2007 01:34:37 +0300 > Petteri Räty <[EMAIL PROTECTED]> wrote: >> Ah found it in the GLEP: >> "The package manager filters the news item and, if it is relevant, >> marks the news item for reading. The package manager should also >> display a notice informing the user that there are unread news items." >> >> This means that adding a >=message is useless as it gets filtered away >> at the first sync. Use elog instead. > > Re-read the GLEP. You're completely misunderstanding the process. > Do you refer to this? Checks for new news messages should be displayed: * After an emerge sync * After an emerge --pretend * Before an emerge (which may also include a red warning message) How can there be new messages with emerge --pretend if emerge --sync is the only way to get them? Should be saying unread messages and it would be clear to me. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [news-item] Paludis 0.24
On Sat, 05 May 2007 01:34:37 +0300 Petteri Räty <[EMAIL PROTECTED]> wrote: > Ah found it in the GLEP: > "The package manager filters the news item and, if it is relevant, > marks the news item for reading. The package manager should also > display a notice informing the user that there are unread news items." > > This means that adding a >=message is useless as it gets filtered away > at the first sync. Use elog instead. Re-read the GLEP. You're completely misunderstanding the process. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
On Sat, 05 May 2007 01:30:05 +0300 Petteri Räty <[EMAIL PROTECTED]> wrote: > So let's say this was a message about package foobar. If it only > affects users after they upgrade it would mean that new installs > would get the news item too, wouldn't it?. Yep. This situation was discussed when designing GLEP 42. There isn't a better alternative because there's no reliable record of packages that used to be installed. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
Petteri Räty kirjoitti: > Alexander Færøy kirjoitti: >> On Sat, May 05, 2007 at 12:13:12AM +0200, Vlastimil Babka wrote: >>> Isn't such use case just a replacement for elog? I thought news were >>> supposed to be delivered before upgrading. Also "You should update your >>> configuration files after upgrading." sounds like something one would >>> read before upgrade... >> It'll only affect users after they upgrade. >> > > So let's say this was a message about package foobar. If it only affects > users after they upgrade it would mean that new installs would get the > news item too, wouldn't it?. Wouldn't the proper behavior be to mark the > item as not applicable when it is first encountered? > > Regards, > Petteri > Ah found it in the GLEP: "The package manager filters the news item and, if it is relevant, marks the news item for reading. The package manager should also display a notice informing the user that there are unread news items." This means that adding a >=message is useless as it gets filtered away at the first sync. Use elog instead. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [news-item] Paludis 0.24
Alexander Færøy kirjoitti: > On Sat, May 05, 2007 at 12:13:12AM +0200, Vlastimil Babka wrote: >> Isn't such use case just a replacement for elog? I thought news were >> supposed to be delivered before upgrading. Also "You should update your >> configuration files after upgrading." sounds like something one would >> read before upgrade... > > It'll only affect users after they upgrade. > So let's say this was a message about package foobar. If it only affects users after they upgrade it would mean that new installs would get the news item too, wouldn't it?. Wouldn't the proper behavior be to mark the item as not applicable when it is first encountered? Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [news-item] Paludis 0.24
On Sat, May 05, 2007 at 12:13:12AM +0200, Vlastimil Babka wrote: > Isn't such use case just a replacement for elog? I thought news were > supposed to be delivered before upgrading. Also "You should update your > configuration files after upgrading." sounds like something one would > read before upgrade... It'll only affect users after they upgrade. -- Alexander Færøy Bugday Lead Alpha/IA64/MIPS Architecture Teams User Relations, Quality Assurance and Release Engineering pgpy0WAahsDWW.pgp Description: PGP signature
Re: [gentoo-dev] [news-item] Paludis 0.24
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Piotr Jaroszyński wrote: > On Friday 04 of May 2007 23:46:39 Thomas Rösner wrote: >> You mean "Display-If-Installed: > No, I want it displayed only after installation of the new version. > Isn't such use case just a replacement for elog? I thought news were supposed to be delivered before upgrading. Also "You should update your configuration files after upgrading." sounds like something one would read before upgrade... - -- Vlastimil Babka (Caster) Gentoo/Java -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGO6/3tbrAj05h3oQRArMcAKCTQIriSODoHFBCI+imBO0RJ/nqKACdEWH/ NOvynKL3uoRP9GXWXwLz0Yc= =Bxw0 -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] [news-item] Paludis 0.24
On Friday 04 of May 2007 23:46:39 Thomas Rösner wrote: > You mean "Display-If-Installed:
Re: [gentoo-dev] [news-item] Paludis 0.24
Hi, Piotr Jaroszyński wrote: > Hello, > > (...) > > Display-If-Installed: >=sys-apps/paludis-0.24 You mean "Display-If-Installed:
[gentoo-dev] [news-item] Paludis 0.24
Hello, Thanks to zmedico we now have support for news items on infra-side and heck they are ready to use. And we should use them! Attaching news item for paludis 0.24. Justification: major config format change. -- Best Regards, Piotr Jaroszyński Title: Changes for Paludis 0.24 Author: Piotr Jaroszyński <[EMAIL PROTECTED]> Content-Type: text/plain Posted: 2007-03-25 Revision: 1 News-Item-Format: 1.0 Display-If-Installed: >=sys-apps/paludis-0.24 As of Paludis 0.24, the use of '*' to match all packages in the Paludis configuration files 'use.conf', 'keywords.conf' and 'licenses.conf' is deprecated in favour of '*/*'. You should update your configuration files after upgrading.
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
On Fri, 2007-05-04 at 20:43 +0100, Ciaran McCreesh wrote: > On Fri, 04 May 2007 15:36:51 -0400 > Chris Gianelloni <[EMAIL PROTECTED]> wrote: > > The point of policy is *not* to impede progress. It is supposed to be > > to provide our users the best quality distribution. If policy gets in > > the way of progress without gain for our users, then the policy needs > > to be revisited. > > And the point of enforcing policy and escalating problems is to prevent > rogue developers from breaking stable, screwing over users' systems and > then repeatedly refusing to show any sign that they've learned from > that and lots of other mistakes. What does enforcement have to do with the Council? The Council approves/enacts policy. We don't do enforcement. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
On Fri, 04 May 2007 15:36:51 -0400 Chris Gianelloni <[EMAIL PROTECTED]> wrote: > The point of policy is *not* to impede progress. It is supposed to be > to provide our users the best quality distribution. If policy gets in > the way of progress without gain for our users, then the policy needs > to be revisited. And the point of enforcing policy and escalating problems is to prevent rogue developers from breaking stable, screwing over users' systems and then repeatedly refusing to show any sign that they've learned from that and lots of other mistakes. -- Ciaran McCreesh signature.asc Description: PGP signature
RE: [gentoo-dev] Monthly Gentoo Council Reminder for May
Lol, its funny that we must concern ourselves with the needs of ""el1te gam3rs"", but I suppose its necessary. Karl Haines -Original Message- From: Chris Gianelloni [mailto:[EMAIL PROTECTED] Sent: Friday, May 04, 2007 2:13 PM To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for May On Thu, 2007-05-03 at 12:15 +0200, "José Luis Rivero (yoswink)" wrote: > Games are not part of core system, so IMHO, use the ~arch branch to have > the latest cool version to enjoy, could be a good way to go for those > el1te gam3rs. We actively discourage users from using ~arch for stable, since it is, well, more stable. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
On Fri, 2007-05-04 at 08:53 -0700, Alec Warner wrote: > I don't even see how this is a policy discussion at all as the policy is > more or less clear to me; is it unclear for others? This is an > enforcement problem, no? No. It *was* an enforcement problem. The problem has been resolved already. There's really no need for the Council to speak on this. Keyword policy applies to everyone. In the cases of certain games, such as Eternal Lands (thanks Roy!), we can make exceptions simply because of the necessity. That being said, there's nothing stopping games (or any maintainer) from filing a stabilization bug *immediately* after putting a package in the tree. I've done it on games a few times and I've seen it done on things like portage when a necessary fix needed to go out as quickly as possible. The point of policy is *not* to impede progress. It is supposed to be to provide our users the best quality distribution. If policy gets in the way of progress without gain for our users, then the policy needs to be revisited. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
On Thu, 2007-05-03 at 12:15 +0200, "José Luis Rivero (yoswink)" wrote: > Games are not part of core system, so IMHO, use the ~arch branch to have > the latest cool version to enjoy, could be a good way to go for those > el1te gam3rs. We actively discourage users from using ~arch for stable, since it is, well, more stable. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
[gentoo-dev] Last rites: binary JWSDP
+# Krzysiek Pawlik <[EMAIL PROTECTED]> (4 May 2007) +# Masked for removal: from source versions are in the +# tree, so please use that. +# Will be removed by end of May. +dev-java/sun-fastinfoset-bin +dev-java/sun-jaxb-bin +dev-java/sun-jaxp-bin +dev-java/sun-jaxr-bin +dev-java/sun-jaxrpc-bin +dev-java/sun-jaxws-bin +dev-java/sun-jwsdp-shared-bin +dev-java/sun-saaj-bin +dev-java/sun-sjsxp-bin +dev-java/sun-wsdp-bin +dev-java/sun-xmldsig-bin +dev-java/sun-xws-security-bin -- Krzysiek Pawlik key id: 0xBC51 desktop-misc, desktop-dock, x86, java, apache, ppc... signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] prep* functions in ebuilds
On Fri, 4 May 2007 18:30:02 +0200 Torsten Veller <[EMAIL PROTECTED]> wrote: > What is with prepalldocs? Is it allowed to use in ebuilds? Should it > be in pms? Or is it just missing in prepall? The prep* functions are Portage internals. They're not suitable for ebuild use and shouldn't be in pms. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] prep* functions in ebuilds
On Friday 04 May 2007, Torsten Veller wrote: > What is with prepalldocs? some people like to install files into /usr/share/doc/$PF/ and not have it be compressed > Is it allowed to use in ebuilds? Should it be in pms? yes > Or is it just missing in prepall? no -mike signature.asc Description: This is a digitally signed message part.
[gentoo-dev] prep* functions in ebuilds
There are two bugs (140697,140699) saying that prepall and prepallman are invoked automatically by portage. Looking at prepall it calls: prepallman prepallinfo prepallstrip What is with prepalldocs? Is it allowed to use in ebuilds? Should it be in pms? Or is it just missing in prepall? Thanks. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
Alan McKinnon wrote: > On Friday 04 May 2007, Jorge Manuel B. S. Vicetto wrote: >> I also don't agree with having an exception for the games herd. As >> others have questioned, how are games more important than security >> bumps? If we were considering exceptions, I would argue that allowing >> the security team to mark packages as stable would make a lot more >> sense, imho. There has never been an exception for games. There is however, no one willing to beat games herd (and others) with a stick sufficiently often that they stop. I don't even see how this is a policy discussion at all as the policy is more or less clear to me; is it unclear for others? This is an enforcement problem, no? -Alec -- [EMAIL PROTECTED] mailing list
[gentoo-dev] It is Bugday time!
Hello! It is Bugday time once again! Join #Gentoo-Bugs on Freenode tomorrow (Saturday) and help us fix as many bugs as possible! Have fun! Best regards, Alexander -- Alexander Færøy Bugday Lead Alpha/IA64/MIPS Architecture Teams User Relations, Quality Assurance and Release Engineering pgpwO7KtEnX3i.pgp Description: PGP signature
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
On Friday 04 May 2007, Jorge Manuel B. S. Vicetto wrote: > I also don't agree with having an exception for the games herd. As > others have questioned, how are games more important than security > bumps? If we were considering exceptions, I would argue that allowing > the security team to mark packages as stable would make a lot more > sense, imho. A quick 2c here from the peanut gallery: Just leave the affected games always keyworded ~arch. The users of games are generally pretty savvy and they know how portage works. You might even find the majority of games players run ~arch boxes anyway so they will never notice that the game ebuild is not in stable alan -- Optimists say the glass is half full, Pessimists say the glass is half empty, Developers say wtf is the glass twice as big as it needs to be? Alan McKinnon alan at linuxholdings dot co dot za +27 82, double three seven, one nine three five -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for May
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. José Luis Rivero (yoswink) wrote: > Roy Marples wrote: >> >> I maintain and play a game called Eternal Lands. I'm a Council member, >> but not part of the games team/herd. >> >> One of the problems games have with stable/unstable/testing/whatever >> keywords is that upstream changes things that in any other application >> just would not change. For example, the network protocol when talking >> to servers. EL is very version specific and when a new client is >> launched, around once every 6 months they change over right away. That >> means our users need the game right away. > > Thanks for the example, trust me if I tell you that we can understand > the situation pretty well. > >> >> I used to commit EL straight to stable for this very reason, but now >> after a few Gentoo QA people bitched EL will never ever have a stable >> keyword. > > I'm nearly sure that you always (at least) compile and run the new > version in your box before you sent it to stable, didn't you? So, at > least, you are able to say that it works in your case. > >> So instead I periodically have to let our users know how to >> unmask EL just so they can play their game. > > There are always ways to educate users about how to use portage properly. > >> So no, in many cases NOT committing straight to stable CAN be >> detrimental to our users if all they want is a games machine. You could >> argue that they shouldn't be using Gentoo, but I would argue why should >> we discriminate? >> > > Ehm, IMHO call it discriminate is a big hard. Are the gnome-2.18 or > beryl users discriminated or they should be using something different to > Gentoo? They only thing people have to do is use some ~arch branch > packages, which isn't too difficult (in Gentoo). > Agreed. All Gentoo beryl users need to use ~arch. I don't think games are so special that we must provide them on stable arch. Afertall, if games are keyworded testing, users can add them to /etc/portage/packaage.keywords if they run a stable system. > This is how I see it: > > Problem with keywording straight to stable is that arch teams are very > zealous about our stable branch. We put a lot of time trying things to > not fail in stable, and if an app is broken, we prefer to not force the > users to compile and install another broken (or unknown to be broken) > version and work to fix the current stable (patches or bumping) together > with the maintainer. > > But if you send things, that you can't try, to stable, the qa baby jesus > will cry if it fails, because nobody has taken care of even compile it > in the arch :) > > Games are not part of core system, so IMHO, use the ~arch branch to have > the latest cool version to enjoy, could be a good way to go for those > el1te gam3rs. > > Thanks. > I also don't agree with having an exception for the games herd. As others have questioned, how are games more important than security bumps? If we were considering exceptions, I would argue that allowing the security team to mark packages as stable would make a lot more sense, imho. Anyway, the important point here for the council meeting is whether our keywording policy is to be enforced or not, regardless of herd, or if / how we want to have exceptions. DISCLAIMER: I have no problems with games. I do like to play some, but I see no problem with using package.keywords. - -- Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org Gentoo-forums / Userrel / Proctors -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGOxXWcAWygvVEyAIRAgv5AJ9k5N/7Uri+rFCxOZllSp2NwmB67gCfepe3 A1Yj3pwuAI3oo/TODP7N79E= =UYbe -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
[gentoo-dev] Last rites: dev-java/violinstrings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > # Alistair Bush <[EMAIL PROTECTED]> (4 May 2007) > # Masked for removal to junkyard in 30 days (3 June) > # Generation 1 ebuild with stale upstream > dev-java/violinstrings Going one, Going Twice, Last and final call!! - -- Alistair John Bush Developer Gentoo Java OpenPGP key 0x4900CFB7 www.gentoo.org www.gentoo.org/proj/en/java -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGOvatRJGZcUkAz7cRAgdAAJwKx3oc412UXaSsq8JEUek9+l1SigCfXOzP IwCNQyAOFRK9DY2y94QmBIk= =r16W -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
