| 1 |
Petteri Räty wrote: |
| 2 |
> http://bugs.gentoo.org/show_bug.cgi?id=163262 |
| 3 |
> |
| 4 |
What is the situation regarding the hooks in general? |
| 5 |
|
| 6 |
> > They're a horrible solution. They don't stack and they override |
| 7 |
> > something that is used by users. What's going to happen if anyone else |
| 8 |
> > starts using the same functions? |
| 9 |
> |
| 10 |
> It's primarily a user feature, introduced due to the usefulness of |
| 11 |
> /etc/portage/bashrc breaking down with proper env state handling. |
| 12 |
> |
| 13 |
<snip> |
| 14 |
> If paludis doesn't want to support (pre|post)_*, whatever, long term it |
| 15 |
> was only a user feature. |
| 16 |
> |
| 17 |
> Short term, it's part of the required env support. |
| 18 |
> |
| 19 |
The "only a user feature" bothers me tbh. Is it so hard to make the |
| 20 |
functions stack then? |
| 21 |
|
| 22 |
(I'm thinking along the lines of an eclass which defines foo_src_unpack |
| 23 |
which can be called by an ebuild function if overridden.) |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives