| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Duncan wrote: |
| 5 |
> Stuart Herbert posted <1130785533.10547.41.camel@××××××××××××××.org>, |
| 6 |
> excerpted below, on Mon, 31 Oct 2005 19:05:33 +0000: |
| 7 |
> |
| 8 |
>>The original problem is that GWN, forums, planet.g.o, gentoo-dev - even |
| 9 |
>>together, we've seen that they just don't reach enough of our user base. |
| 10 |
>>Aren't we just going to reach the same people by putting more news in |
| 11 |
>>the same old place? How is that going to reach the people we're not |
| 12 |
>>reaching today? |
| 13 |
> |
| 14 |
> |
| 15 |
> There is /one/ way to reach /everyone/ doing an upgrade (well, those that |
| 16 |
> do emerge -a or -p, anyway, and those that don't, well... they apparently |
| 17 |
> /like/ being left in the dark, and doing perhaps risky upgrades without |
| 18 |
> knowing what's going on, so let's not disturb their "enjoyment" <g>). |
| 19 |
> |
| 20 |
> That ONE way: Push a "null" portage -rX upgrade to both stable and ~ |
| 21 |
> versions, the sole purpose of which is to print the *VITALLY* *IMPORTANT* |
| 22 |
> *ANNOUNCEMENT* as an einfo both after the "upgrade", and as part of the |
| 23 |
> "portage will stop merging at this point and recalculate" message one gets |
| 24 |
> with a -p or -a. (For double-sure effect, make the first emerge action |
| 25 |
> after the upgrade /only/ print the message, doing nothing else. Further |
| 26 |
> emerges would then go back to normal behavior.) |
| 27 |
> |
| 28 |
|
| 29 |
Cramming this info in portage is stupid, because portage is supposed to |
| 30 |
be NON-interactive. Does anyone really expect users to sit and stare at |
| 31 |
the output of a compile (openoffice takes HOURS to compile) waiting for |
| 32 |
an einfo to pass by? |
| 33 |
|
| 34 |
Perhaps printing out an URI after portage is done would be useful: |
| 35 |
|
| 36 |
http://errata.g.o/apache-migration.xml |
| 37 |
|
| 38 |
Publishing the info on a webpage also allows you to view the info from |
| 39 |
another computer if you seriously b0rk something during an upgrade. |
| 40 |
-----BEGIN PGP SIGNATURE----- |
| 41 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 42 |
|
| 43 |
iD8DBQFDahOq2QTTR4CNEQARAg/mAJ9/Lbfpq0McjxI3isOopxLo60q1ugCdH5Ux |
| 44 |
++iU1lMgWKCaxgybqQzUdIs= |
| 45 |
=B+rI |
| 46 |
-----END PGP SIGNATURE----- |
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives