| 1 |
On Monday 25 July 2005 16:51, Martin Schlemmer wrote: |
| 2 |
> On Sat, 2005-07-23 at 11:18 -0400, Greg KH wrote: |
| 3 |
> > On Sat, Jul 23, 2005 at 10:53:15AM -0400, Alec Warner wrote: |
| 4 |
> > > Georgi Georgiev wrote: |
| 5 |
> > > > Just to make sure I am not missing something. |
| 6 |
> > > > |
| 7 |
> > > > Does this cover the |
| 8 |
> > > > |
| 9 |
> > > > - If you are upgrading from a version of udev prior to 046 ... |
| 10 |
> > > > - If you are upgrading from a version of udev prior to 050 ... |
| 11 |
> > > > - If you are upgrading from a version of udev prior to 057 ... |
| 12 |
> > > > - If you are upgrading from a version of udev prior to 059 ... |
| 13 |
> > > > |
| 14 |
> > > > cases automatically? I.e. *not* showing irrelevant warnings on every |
| 15 |
> > > > upgrade/rebuild. |
| 16 |
> > > > |
| 17 |
> > > |
| 18 |
> > > The writer of pkg_warn() could do this, it's still in the ebuild and |
| 19 |
> > > could use the normal ebuild functions to determine what the user is |
| 20 |
> > > running ( has_version() and whatnot ) and then run a case statement on that. |
| 21 |
> > |
| 22 |
> > Great, anyone care to send me a patch for the udev ebuild to do this so |
| 23 |
> > not everyone sees this message? It will only get longer over time... |
| 24 |
> > |
| 25 |
> |
| 26 |
> Something like this maybe? (Yes, I know using $T will be frowned upon, |
| 27 |
> but not much else you can do. Also, might use has_version(), but that |
| 28 |
> is more difficult to parse, and I figured you normally only want those |
| 29 |
> for system udev ...) |
| 30 |
|
| 31 |
Combining the pkg_preinst and pkg_postinst parts (and removing the usage |
| 32 |
of $T ;), that pretty much shows exactly what the proposed pkg_warn would |
| 33 |
look like. Only difference being that it would be executed before emerging |
| 34 |
starts. |
| 35 |
|
| 36 |
-- |
| 37 |
Jason Stubbs |
Archives