1 |
On Mon, 2005-07-25 at 22:33 +0900, Jason Stubbs wrote: |
2 |
> On Monday 25 July 2005 22:09, Martin Schlemmer wrote: |
3 |
> > On Mon, 2005-07-25 at 20:53 +0900, Jason Stubbs wrote: |
4 |
> > > On Monday 25 July 2005 16:51, Martin Schlemmer wrote: |
5 |
> > > > Something like this maybe? (Yes, I know using $T will be frowned upon, |
6 |
> > > > but not much else you can do. Also, might use has_version(), but that |
7 |
> > > > is more difficult to parse, and I figured you normally only want those |
8 |
> > > > for system udev ...) |
9 |
> > > |
10 |
> > > Combining the pkg_preinst and pkg_postinst parts (and removing the usage |
11 |
> > > of $T ;), that pretty much shows exactly what the proposed pkg_warn would |
12 |
> > > look like. Only difference being that it would be executed before emerging |
13 |
> > > starts. |
14 |
> > |
15 |
> > Currently: |
16 |
> > - if everything is moved to pkg_preinst(), the message will not show at |
17 |
> > the end of the merge, so much higher chance of getting missed. |
18 |
> > - if everything is moved to pkg_postinst(), $udev_version will be the |
19 |
> > new version, and be of no use. |
20 |
> > - if you meant that this is for the pkg_warn() ... it still wont really |
21 |
> > help that much, as it will differ from before/after the update :/ |
22 |
> |
23 |
> What's the issue with pkg_warn? It would only be ran before the update, |
24 |
> so the ebuild it's in is the new version and the current version can be |
25 |
> obtained with has_version. |
26 |
> |
27 |
|
28 |
Ah, ok, guess I should read more carefully next time =) |
29 |
|
30 |
|
31 |
-- |
32 |
Martin Schlemmer |