Re: [gentoo-dev] no more time for SynCE
On Tue, 2011-04-12 at 11:35 +0200, Angelo Arrifano wrote: > On Seg, 2011-04-11 at 17:33 +0300, Samuli Suominen wrote: > > On 04/11/2011 03:01 AM, Iain Buchanan wrote: > > > [2] https://synce.svn.sourceforge.net/svnroot/synce/dist/gentoo > Hello, > > I want to help in sanitizing the overlay and bring the ebuilds into > portage. We can see that next weekend if you have the time. > > Regards, Hi & thanks, contact the SynCE devs on sourceforge or via synce-de...@lists.sourceforge.net to get write access, I'm sure they would be pleased. If the current version is in the tree, then most of the overlay can be removed, with perhaps the exception of synce-kpm and synce-gnome. I won't be around the next couple of weekends but I'm happy to respond to emails when I can, if I can help. -- Iain Buchanan
Re: [gentoo-dev] Re: openrc portage news item
Hi Matt, On Thu, Apr 14, 2011 at 10:41:23AM -0500, Matthew Summers wrote: > 1. We should determine and then announce the precise date (appears to > be in May) and time that baselayout-2 will be stabilized via: > 1.1 A front page News item on www.g.o (PR team assemble!), > 1.2 The main MLs (gentoo-announce, gentoo-users, etc), > 1.3 Add a link to the www news item to /topic in #gentoo, and > 1.4 Post a sticky topic in the Forum. > all in addition to the eselect news item under discussion here. The > above would link to the migration guide too. The problem is that the date is still subject to change. If we get more bugs that we think should block stabilization, those would be fixed, then a new release put out, then we are back to waiting 30 days unless we make an exception to the 30 day rule. > 2. We should prepare a quick "recover-your-system" guide (could also > create a script too) that can be quickly linked to for user support. > This will save time for people providing support via IRC, email, etc, > and give people a reasonable means of system recovery without huge > pain. As far as I know, the only thing that can go wrong here is rebooting after installing bl2/openrc without following the migration guide. If you do that, the only thing you can do is boot a live cd, chroot into the system and follow the migration guide from there. There's not really a way I know of that we could write a script to do that. > 3. Update the handbook to reflect these changes as soon as possible, > and have that all go public simultaneously with the stabilization. There is a bug that is blocked by the tracker for this. > 4. I have attached an edited and unfinished version of the original > news item for review. I attempted to be succinct. Ok, I took your news item, and I'll look it over. I may add more to it about what will happen if you do not follow the migration guide. pgphF1gkzJGmd.pgp Description: PGP signature
[gentoo-dev] About dropping us from dev-dotnet/mysql-connector-net maintainership
Was unable to bump it for a long time, don't use it, don't even know how to use it, nobody in dotnet team is willing to maintain it just now. If you want to take its maintainership, please tell us so, if nobody volunteers, will be moved to maintainer-needed next week Thanks a lot signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Re: openrc portage news item
Matthew Summers wrote: Hi, I have a few suggestions regarding this major change to Gentoo systems. 1. We should determine and then announce the precise date (appears to be in May) and time that baselayout-2 will be stabilized via: 1.1 A front page News item on www.g.o (PR team assemble!), 1.2 The main MLs (gentoo-announce, gentoo-users, etc), 1.3 Add a link to the www news item to /topic in #gentoo, and 1.4 Post a sticky topic in the Forum. all in addition to the eselect news item under discussion here. The above would link to the migration guide too. The rationale for this effort at getting the word out is to prevent users from hosing their system(s). While I tend to agree that users should read these eselect news items, its often not the case. Therefore I recommend shooting for the widest possible distribution of this information. Also, this gives PR a chance to let the world know about openrc and its benefits to Gentoo. 2. We should prepare a quick "recover-your-system" guide (could also create a script too) that can be quickly linked to for user support. This will save time for people providing support via IRC, email, etc, and give people a reasonable means of system recovery without huge pain. 3. Update the handbook to reflect these changes as soon as possible, and have that all go public simultaneously with the stabilization. 4. I have attached an edited and unfinished version of the original news item for review. I attempted to be succinct. This is a really exciting and potentially also rather anxiety-provoking change for our user base and Gentoo. We all know that the new baselayout is awesome, and users will find out soon enough. We simply need to make our best effort at easing the transition so we minimize the number of casualties. Thank you, Matt I wouldn't mind seeing this on the main Gentoo page as soon as possible. Some people may not visit the Gentoo page very often, I'm one of those. This could be done even if it has to be changed as things update. Maybe one that it is coming and one a few days before it hits stable in the tree. +1 on this being a good idea. This is a really important update since it can cause a system to be unbootable. I'm thinking about folks that may admin a box remotely too. If all the above is done and people miss that it is coming, I think it could safely be said that everything that could be done was done to inform people. The list above includes about every means of communication Gentoo has. Great post. Dale :-) :-)
Re: [gentoo-dev] Re: openrc portage news item
Hi, I have a few suggestions regarding this major change to Gentoo systems. 1. We should determine and then announce the precise date (appears to be in May) and time that baselayout-2 will be stabilized via: 1.1 A front page News item on www.g.o (PR team assemble!), 1.2 The main MLs (gentoo-announce, gentoo-users, etc), 1.3 Add a link to the www news item to /topic in #gentoo, and 1.4 Post a sticky topic in the Forum. all in addition to the eselect news item under discussion here. The above would link to the migration guide too. The rationale for this effort at getting the word out is to prevent users from hosing their system(s). While I tend to agree that users should read these eselect news items, its often not the case. Therefore I recommend shooting for the widest possible distribution of this information. Also, this gives PR a chance to let the world know about openrc and its benefits to Gentoo. 2. We should prepare a quick "recover-your-system" guide (could also create a script too) that can be quickly linked to for user support. This will save time for people providing support via IRC, email, etc, and give people a reasonable means of system recovery without huge pain. 3. Update the handbook to reflect these changes as soon as possible, and have that all go public simultaneously with the stabilization. 4. I have attached an edited and unfinished version of the original news item for review. I attempted to be succinct. This is a really exciting and potentially also rather anxiety-provoking change for our user base and Gentoo. We all know that the new baselayout is awesome, and users will find out soon enough. We simply need to make our best effort at easing the transition so we minimize the number of casualties. Thank you, Matt -- Matthew W. Summers Title: Baselayout update Author: Christian Faulhammer Author: William Hubbs Content-Type: text/plain Posted: 2011-05-01 Revision: 1 News-Item-Format: 1.0 Display-If-Installed: http://www.gentoo.org/doc/en/openrc-migration.xml FAILURE TO FOLLOW THE MIGRATION GUIDE CAN RESULT IN AN UNBOOTABLE SYSTEM! For more information or supprt regarding this change please see the following: - link to news item (should contain info regarding where to obtain support) - link to recover-system guide - link to handbook
Re: [gentoo-dev] Re: openrc portage news item
Duncan wrote: > From my read, while it does actually say it's important, the politeness with which it does so don't well convey the true importance and urgency of the situation. If there's a fire, you don't say "Please, excuse me for interrupting, but there's a fire and at your convenience, please make your way to the exit." Rather, it's "*FIRE*! Please STAY CALM. WALK DON'T RUN. The exit is OVER THERE. Make your way to it IMMEDIATELY!" So more along the lines of: """ After installing these packages, please DO NOT REBOOT until you follow the upgrade guide located at http://www.gentoo.org/doc/en/openrc-migration.xml. If you do not follow the guide as soon as possible after these packages are upgraded and you reboot or crash without doing so, the system will likely fail to boot properly, and you may be looking at some time in manual recovery mode to fix it. """ Yes, the DO NOT REBOOT is shouting, not exactly polite, but that's arguably what's called for in this situation. Plus having it in all caps makes it stand out. If a person even looks at the message, they will see that at least. Then hopefully, they will read the rest. I think bold would be nice to tho. It's not like this is not really really important. Even with that, I see a few people not even noticing it and the next reboot going badly. Dale :-) :-)
Re: [gentoo-dev] Make usage and warnings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/14/2011 03:48 AM, Tomá? Chvátal wrote: > Hi guys, > currently in main tree we have quite few places where direct make calls are > used instead of emake. > > Most of these are just poor excuses to avoid setting -j1 bit later. This > soultion is problematic because users can set more make options and they all > get ignored this way. > > I would like to propose repoman warning that would report direct make usage > and possibly fill the bugs where relevant so it gets migrated to "emake -j1" > (or whatever else is required). > > Cheers +1 I also am a big proponent of *not* using -j1 unless it is 100% necessary. Fix the Makefile. Don't just take the shortcut. There is a tracker for that here [1]. [1] http://bugs.gentoo.org/show_bug.cgi?id=351559 Regards, - -- Dane Smith (c1pher) Gentoo Linux Developer -- QA / Crypto / Sunrise / x86 RSA Key: http://pgp.mit.edu:11371/pks/lookup?search=0x0C2E1531&op=index -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJNpuqOAAoJEEsurZwMLhUxIC4P/j+n2IUjII3SK02Fr37paeax X8J6DqvvZXKyW7ZeIHq9Nqr2EoSMLv+BnyA9O6tcNUayV/Z0/PbkI1+0Dod05mvv AVWEZ+Ya0TGZ8e1UbsUqphjis0qcDMgTDcUJTnsbFRGe6J8LdEx5BanLlZd/2Vcv 5hQG+tuY1IYTfadyBR8fgcAkY2AXTe5JD2UaV7XZKwt99f8FdM23hx9ZUoO+l1g5 IzYkiVnfNSmMNyujtxUW4yBHVQcXTCfWCgyyuWbHaB9aGN/FN4QCvP+0A36FOron vt+iKGcihpyKSGGVHbQ36H8T5c/6QXlX65QPuWVHTTAi2gth3ckmEqtSH8kaE0R9 +5pHB5Afye1HFlggR3oxmRSGKpAHksuSahbxyU8o1hVbDpugaP5yZMAqKT2hAkcQ j5ZM/kjhv9yOi4ddfVtW4M3UA5+FStDrmZA1sq3w6OjJv3NkyyApi8AeETde6Mva tcAxmdAHiFSiFCPlSC5pN5Yx/RQPwY8q0tFGmdsQ2Se/5buzhXE4j8ll7cokMsTE RvN/LvBY+5wZDQ1TpW5umNE/m770AG7dgci5eai1WfhYvGN2h11XyLfI1BdNhEpS 2+jjp/hcsCUdwuqIJw9OogSpxleRhceLJovEHvCVcByRQJK0rBAE1IF/TytJqrj/ qUABZoc/worAfjle9zLh =ZrdI -END PGP SIGNATURE-
Re: [gentoo-dev] Re: openrc portage news item
On Thu, Apr 14, 2011 at 4:09 AM, Duncan <1i5t5.dun...@cox.net> wrote: > FWIW/IMHO, I don't believe the news item needs mentioning that it was bash > that made it slow and inflexible. Most users don't so much care whether > it's C or bash or java that made it so, only that it was. If this were Ubuntu I'd be inclined to agree. However, I think that most Gentoo users would be interested. Maybe I have a different perspective because I just gave a talk on booting two nights ago at an LUG, but I wasn't even the one to bring up the shortcomings of bash in the typical linux SysVInit-based service scripts. Various approaches that were discussed included symlinking /bin/sh to dash instead of bash, and C-based solutions (or a combination of both). It was interesting to hear that at least a few other distros struggle with bashisms in their init scripts, but no so much due to licensing/BSD issues but because of a desire to use dash which does not support all bashisms. No need to go into gory details, but mentioning that it is C-based instead of bash-based seems reasonable. Granted, we're not really getting rid of one of the problems with bash, which isn't just /sbin/rc but rather it includes the init scripts themselves (every one of which requires spawning a new bash, and many spawn additional processes like sed/awk/etc). Rich
Re: [gentoo-dev] openrc portage news item
2011/4/14 Thomas Beierlein > On Thu, 14 Apr 2011 12:51:55 +0200 > Tomá? Chvátal wrote: > > > On Thursday 14 of April 2011 13:32:04 Kfir Lavi wrote: > > > When i run world update, I usually don't really check all the > > > written stuff. > > > > > > If I do this, I'm sure a lot more Gentoo users do the same. > > > So do expect people rebooting the machine without checking what > > > your have wrote. > > > This can be a major headache if you have few systems that are doing > > > auto updates. > > > I would solve this issue by stopping the emerge and getting the > > > attention of the user. > > > If I don't get the attention of the user, no openrc will be > > > installed. It should be something like emerge -C ... 1 .2 3 4 5... > > > > > > To conclude, you can't issue such a change without proper > > > confirmation from the user. > > > > > This was discussed multiple times, news items are to be read. > > Users ignore elog informations/web announcements/... so it was agreed > > that news item is agressive enough to user so they must read it. > > If they don't do so it is just their fault. > > And no runtime changing for portage where it expect some input is > > seriously stupid idea, most of us script updates in batch and noone > > would actualy read it. > > > > Never the less as I said we expect user to read that stuff and if he > > does not he is on his own due to his dumb approach. > > Maybe we should underline our intention by having that policy > documented in the installation handbook. A good place may be section 2 > "Working with > Gentoo" (http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2). > > At least all newbies will stumble upon it once. > > Regards, > Thomas. > Yeah, before the stabilization of OpenRc and Baselayout 2.x, the Gentoo handbook really need to be updated too. I don't see how a newbie should be able to install his box with an outdated handbook. -- Salut alp Sylvain
Re: [gentoo-dev] openrc portage news item
On Thu, 14 Apr 2011 12:51:55 +0200 Tomá? Chvátal wrote: > On Thursday 14 of April 2011 13:32:04 Kfir Lavi wrote: > > When i run world update, I usually don't really check all the > > written stuff. > > > > If I do this, I'm sure a lot more Gentoo users do the same. > > So do expect people rebooting the machine without checking what > > your have wrote. > > This can be a major headache if you have few systems that are doing > > auto updates. > > I would solve this issue by stopping the emerge and getting the > > attention of the user. > > If I don't get the attention of the user, no openrc will be > > installed. It should be something like emerge -C ... 1 .2 3 4 5... > > > > To conclude, you can't issue such a change without proper > > confirmation from the user. > > > This was discussed multiple times, news items are to be read. > Users ignore elog informations/web announcements/... so it was agreed > that news item is agressive enough to user so they must read it. > If they don't do so it is just their fault. > And no runtime changing for portage where it expect some input is > seriously stupid idea, most of us script updates in batch and noone > would actualy read it. > > Never the less as I said we expect user to read that stuff and if he > does not he is on his own due to his dumb approach. Maybe we should underline our intention by having that policy documented in the installation handbook. A good place may be section 2 "Working with Gentoo" (http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2). At least all newbies will stumble upon it once. Regards, Thomas. signature.asc Description: PGP signature
Re: [gentoo-dev] openrc portage news item
El jue, 14-04-2011 a las 12:51 +0200, Tomá? Chvátal escribió: > On Thursday 14 of April 2011 13:32:04 Kfir Lavi wrote: > > When i run world update, I usually don't really check all the written stuff. > > > > If I do this, I'm sure a lot more Gentoo users do the same. > > So do expect people rebooting the machine without checking what your have > > wrote. > > This can be a major headache if you have few systems that are doing auto > > updates. > > I would solve this issue by stopping the emerge and getting the attention of > > the user. > > If I don't get the attention of the user, no openrc will be installed. > > It should be something like emerge -C ... 1 .2 3 4 5... > > > > To conclude, you can't issue such a change without proper confirmation from > > the user. > > > This was discussed multiple times, news items are to be read. > Users ignore elog informations/web announcements/... so it was agreed that > news item is agressive enough to user so they must read it. > If they don't do so it is just their fault. > And no runtime changing for portage where it expect some input is seriously > stupid idea, most of us script updates in batch and noone would actualy read > it. > > Never the less as I said we expect user to read that stuff and if he does not > he is on his own due to his dumb approach. I also thought about this problem: I usually read news items before updating, but I have also seen how other people with root access to other machines I mainly maintain forget from time to time to do so. This is why I opened: http://bugs.gentoo.org/show_bug.cgi?id=363567 As news items are really there to be read BEFORE updating, I think that it should be enforced to prevent people from updating before reading them (I have also read Lars comment, I obviously have no problem at all with adding some option to revert this behavior, but I still think default behavior should be to prevent update if news items are not read). signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] openrc portage news item
On Thursday 14 of April 2011 13:32:04 Kfir Lavi wrote: > When i run world update, I usually don't really check all the written stuff. > > If I do this, I'm sure a lot more Gentoo users do the same. > So do expect people rebooting the machine without checking what your have > wrote. > This can be a major headache if you have few systems that are doing auto > updates. > I would solve this issue by stopping the emerge and getting the attention of > the user. > If I don't get the attention of the user, no openrc will be installed. > It should be something like emerge -C ... 1 .2 3 4 5... > > To conclude, you can't issue such a change without proper confirmation from > the user. > This was discussed multiple times, news items are to be read. Users ignore elog informations/web announcements/... so it was agreed that news item is agressive enough to user so they must read it. If they don't do so it is just their fault. And no runtime changing for portage where it expect some input is seriously stupid idea, most of us script updates in batch and noone would actualy read it. Never the less as I said we expect user to read that stuff and if he does not he is on his own due to his dumb approach. -- Tomáš Chvátal Gentoo Linux Developer [Cluster/Council/KDE/QA/Sci/X11] E-Mail : scarab...@gentoo.org GnuPG FP: 94A4 5CCD 85D3 DE24 FE99 F924 1C1E 9CDE 0341 4587 GnuPG ID: 03414587 signature.asc Description: This is a digitally signed message part.
[gentoo-dev] cmake.eclass turns OFF essential flags
Hi, I'm using cmake as my build system. I have created few cmake modules that are installed in another package. I now want to use those modules, when running cmake for current install. Cmake finds extra modules using CMAKE_MODULE_PATH. When running cmake manually, things work well, but when it's run under an ebuild which use: EAPI="3" inherit cmake-utils flag-o-matic The emerge will stop complaining that it can't find the extra modules. Printing the CMAKE_MODULE_PATH shows that it is OFF. What I understand is: cmake.eclass will turn OFF all the flags. I have looked in the code, but didn't find the place which is turning all flags off. Is there a way to solve this problem? Maybe a flag for cmake.eclass that will cause respecting the users initial settings? I can solve this problem instantly by installing my extra cmake modules into the main cmake modules directory, but then I'm mixing 2 packages, which I really don't want to do. Regards, Kfir
Re: [gentoo-dev] openrc portage news item
On Wed, Apr 13, 2011 at 9:15 PM, William Hubbs wrote: > All, > > this is the portage news item I am planning on committing to the tree. > > This is based on an earlier version written by Christian Fallhammer. > > If there are no suggestions for additions or corrections, this will be > committed on 5/1. > > Thanks, > > William > > Hi, When i run world update, I usually don't really check all the written stuff. If I do this, I'm sure a lot more Gentoo users do the same. So do expect people rebooting the machine without checking what your have wrote. This can be a major headache if you have few systems that are doing auto updates. I would solve this issue by stopping the emerge and getting the attention of the user. If I don't get the attention of the user, no openrc will be installed. It should be something like emerge -C ... 1 .2 3 4 5... To conclude, you can't issue such a change without proper confirmation from the user. Regards, Kfir
[gentoo-dev] Re: openrc portage news item
Dirkjan Ochtman posted on Thu, 14 Apr 2011 09:21:48 +0200 as excerpted: > On Thu, Apr 14, 2011 at 07:30, justin wrote: >> To me, it doesn't makes it totally clear that you screw everything when >> rebooting before following the guide. Perhaps this should be made much >> clearer. > > Huh? > > "After you install these packages, please do not reboot your system > until you follow the upgrade guide located at > http://www.gentoo.org/doc/en/openrc-migration.xml. > > It is important that you follow the guide as soon as possible after > these packages are upgraded. Otherwise, there is a chance that your > system will not reboot properly." > > Seem quite clear to me. >From my read, while it does actually say it's important, the politeness with which it does so don't well convey the true importance and urgency of the situation. If there's a fire, you don't say "Please, excuse me for interrupting, but there's a fire and at your convenience, please make your way to the exit." Rather, it's "*FIRE*! Please STAY CALM. WALK DON'T RUN. The exit is OVER THERE. Make your way to it IMMEDIATELY!" So more along the lines of: """ After installing these packages, please DO NOT REBOOT until you follow the upgrade guide located at http://www.gentoo.org/doc/en/openrc-migration.xml. If you do not follow the guide as soon as possible after these packages are upgraded and you reboot or crash without doing so, the system will likely fail to boot properly, and you may be looking at some time in manual recovery mode to fix it. """ Yes, the DO NOT REBOOT is shouting, not exactly polite, but that's arguably what's called for in this situation. -- 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
Re: [gentoo-dev] openrc portage news item
On 14/04/11 09:21, Dirkjan Ochtman wrote: > On Thu, Apr 14, 2011 at 07:30, justin wrote: >> To me, it doesn't makes it totally clear that you screw everything when >> rebooting before following the guide. Perhaps this should be made much >> clearer. > > Huh? > > "After you install these packages, please do not reboot your system > until you follow the upgrade guide located at > http://www.gentoo.org/doc/en/openrc-migration.xml. > > It is important that you follow the guide as soon as possible after > these packages are upgraded. Otherwise, there is a chance that your > system will not reboot properly." > > Seem quite clear to me. > > Cheers, > > Dirkjan _Underline_ or write it capital, I don't know. For us and those who know gentoo this is clear. But user tend to over read things. I would do a bet that a number of people will cry, because they just rebooted, because they stopped reading till there; beside those who do not even read the news item. So really would suggest doing ugly things like *ATTENTION* or so. justin signature.asc Description: OpenPGP digital signature
[gentoo-dev] Re: openrc portage news item
William Hubbs posted on Wed, 13 Apr 2011 14:58:51 -0500 as excerpted: > On Wed, Apr 13, 2011 at 08:41:16PM +0200, "Pawe?? Hajdan, Jr." wrote: >> On 4/13/11 8:15 PM, William Hubbs wrote: >> > The baselayout package provides files which all systems must have in >> > order to function properly. You are currently using version 1.x, >> > which has several issues. The most significant of these is that the >> > included init system is written entirely in bash, which makes it slow >> > and not very flexable. >> >> I think it would be worth it to mention other problems too (just a list >> of most important bugs if that makes sense). > > Does anyone on the list have any particular suggestions for what should > be mentioned? The definition of "important" might vary per person, but, while it has been awhile since I ran baselayout-1, here's what I recall that I'd consider significant. 1) While baselayout-1 had a parallel boot option, it was quite broken and (partly or entirely, not sure which) non-functional. The same thing in baselayout-2/openrc works WELL and I use it all the time. (Given the emphasis placed on this in the media, the various boot-timing contests, etc, and the fact that this feature puts Gentoo in-play again in regard to speed-boots, it's a pretty big positive in favor of upgrading.) 2) In baselayout-1, the early-boot wasn't actually dependency based, but rather, was strict-serial-order based on a list of IIRC four services started in the exact order they were listed. (clock or whatever the baselayout-1 name was, was one of them, IDR the others). OpenRC/ baselayout-2 is fully dependency based at every stage. I mentioned both of these points earlier in a different context. FWIW/IMHO, I don't believe the news item needs mentioning that it was bash that made it slow and inflexible. Most users don't so much care whether it's C or bash or java that made it so, only that it was. I'd personally put more emphasis on the /how/ instead of the /why/, as I believe that's what most users want to know. The above two points support that, thus, reworking that whole bit: """ You are currently using version 1.x, which was slow and inflexible. It was slow in part because the parallel boot option was broken, and inflexible in part because dependencies didn't work until later in the boot process, so the first few services had to be started in order according to an arbitrary list. """ No mention of bash as a reason because that's an internal implementation deal I as an admin don't want or need to care about. What difference will it make in the way my system boots and how will that be better, that's what I as an admin want to know. (That said, the above can surely be improved as well. The ideas conveyed are better I believe, more direct to what a Gentoo user/admin will likely want to know, but I'm my wording isn't right, yet.) -- 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
[gentoo-dev] Make usage and warnings
Hi guys, currently in main tree we have quite few places where direct make calls are used instead of emake. Most of these are just poor excuses to avoid setting -j1 bit later. This soultion is problematic because users can set more make options and they all get ignored this way. I would like to propose repoman warning that would report direct make usage and possibly fill the bugs where relevant so it gets migrated to "emake -j1" (or whatever else is required). Cheers -- Tomáš Chvátal Gentoo Linux Developer [Cluster/Council/KDE/QA/Sci/X11] E-Mail : scarab...@gentoo.org GnuPG FP: 94A4 5CCD 85D3 DE24 FE99 F924 1C1E 9CDE 0341 4587 GnuPG ID: 03414587 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] openrc portage news item
On Thu, Apr 14, 2011 at 07:30, justin wrote: > To me, it doesn't makes it totally clear that you screw everything when > rebooting before following the guide. Perhaps this should be made much > clearer. Huh? "After you install these packages, please do not reboot your system until you follow the upgrade guide located at http://www.gentoo.org/doc/en/openrc-migration.xml. It is important that you follow the guide as soon as possible after these packages are upgraded. Otherwise, there is a chance that your system will not reboot properly." Seem quite clear to me. Cheers, Dirkjan
