| 1 |
On 03/05/2010 10:14 PM, Ryan Hill wrote: |
| 2 |
> |
| 3 |
> Because then people use them. Don't ask me why. I have things I deprecated |
| 4 |
> over two years ago still being used by a dozen ebuilds bumped within the last |
| 5 |
> three months. You should be familiar with this behaviour wrt. |
| 6 |
> built_with_use. So, when I'm making changes I still have to maintain the |
| 7 |
> deprecated stuff. |
| 8 |
> |
| 9 |
|
| 10 |
built_with_use isn't using eerror and it wasn't scanned by repoman so |
| 11 |
unless you read the whole ebuild you could miss it when bumping. If we |
| 12 |
have devs ignoring eerrors out of the ebuild, then we should rather get |
| 13 |
rid of them. It's much harder to spot you are using a deprecated |
| 14 |
function when it doesn't exist at all as then the error message during |
| 15 |
emerge doesn't stand out in any form. |
| 16 |
|
| 17 |
Regards, |
| 18 |
Petteri |
Archives