| 1 |
Ok for the 'typos' kind of changes ... maybe I had exagerated my examples. |
| 2 |
But still, it would be nice to have some level of criticality related |
| 3 |
to updates. |
| 4 |
|
| 5 |
A highly important security bug fix would need to be updated in a |
| 6 |
matter of hours while a functionality enhancement could wait for a |
| 7 |
maintenance window a few weeks later. I love the idea of being able |
| 8 |
to have constant up-to-date servers but I'd love to be able to update |
| 9 |
the important things quickly and do all the other updates at a later time. |
| 10 |
|
| 11 |
One could say "how can we judge if an update is important/critical" ... |
| 12 |
I'd answer that the one that is doing the ebuild surely has a good idea |
| 13 |
of the importance of the change. |
| 14 |
|
| 15 |
It's late here too, I'm not sure I'm pretty clear ... let me give a |
| 16 |
visual example : |
| 17 |
|
| 18 |
|
| 19 |
emerge --critical --pretend --update world |
| 20 |
[ebuild U ] sys-libs/pam-0.77 [0.75-r11] |
| 21 |
[ebuild U ] sys-apps/pam-login-3.14 [3.11] |
| 22 |
[ebuild U ] net-misc/openssh-3.7.1_p2-r2 [3.7.1_p2-r1] |
| 23 |
|
| 24 |
|
| 25 |
emerge --pretend --update world |
| 26 |
[ebuild U ] sys-devel/libperl-5.8.2 [5.8.0] |
| 27 |
[ebuild U ] dev-lang/perl-5.8.2-r1 [5.8.0-r12] |
| 28 |
[ebuild U ] sys-libs/ncurses-5.4 [5.3-r5] |
| 29 |
[ebuild U ] sys-devel/bison-1.875 [1.35] |
| 30 |
[ebuild U ] sys-devel/gcc-3.3.2-r5 [3.2.3-r3] |
| 31 |
[ebuild U ] sys-libs/pam-0.77 [0.75-r11] |
| 32 |
[ebuild U ] sys-apps/pam-login-3.14 [3.11] |
| 33 |
[ebuild U ] app-shells/bash-2.05b-r9 [2.05b-r7] |
| 34 |
[ebuild U ] net-misc/openssh-3.7.1_p2-r2 [3.7.1_p2-r1] |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
On Tue, 2 Mar 2004, André Ventura Lemos wrote: |
| 43 |
|
| 44 |
> Yhea, I kind of remember that, things just get quietly fixed in the cvs. |
| 45 |
> |
| 46 |
> seems ok to me |
| 47 |
> |
| 48 |
> On Tue, 2004-03-02 at 01:33, Michael Cummings wrote: |
| 49 |
> > Technically speaking (ok, so this is in policy somewhere at some point in |
| 50 |
> > time, it's late, I'm tired) if it's a typo fix, the ebuild isn't bumped - |
| 51 |
> > bumps (should) only occur when the change affects the code that is produced, |
| 52 |
> > or otherwise alters/enhances functionality. |
| 53 |
> > |
| 54 |
> > -mike, just a perl guy |
| 55 |
> |
| 56 |
> |
| 57 |
> -- |
| 58 |
> I/O, I/O, |
| 59 |
> It's off to disk I go, |
| 60 |
> A bit or byte to read or write, |
| 61 |
> I/O, I/O, I/O... |
| 62 |
> |
| 63 |
|
| 64 |
|
| 65 |
-- |
| 66 |
gentoo-dev@g.o mailing list |
Archives