| 1 |
On Thu, 15 Oct 2015 18:15:42 -0400 |
| 2 |
Rich Freeman <rich0@g.o> wrote: |
| 3 |
|
| 4 |
> On Thu, Oct 15, 2015 at 6:00 PM, Zac Medico <zmedico@g.o> |
| 5 |
> wrote: |
| 6 |
> > On 10/15/2015 02:51 PM, Anthony G. Basile wrote: |
| 7 |
> > |
| 8 |
> >> The only change in moving it to @profile is the warning. |
| 9 |
> > |
| 10 |
> > What's the point of getting rid of the warning if the package is |
| 11 |
> > going to get pulled back in on the next @world update? Either way, |
| 12 |
> > the end result it that the user has to go through some hoops |
| 13 |
> > (/etc/portage/profile overrides) if they don't want that package |
| 14 |
> > installed again. |
| 15 |
> |
| 16 |
> ++ |
| 17 |
> |
| 18 |
> I think just pre-seeding the world file is a simpler solution. Users |
| 19 |
> can just uninstall the files normally then. |
| 20 |
|
| 21 |
|
| 22 |
+1 |
| 23 |
|
| 24 |
|
| 25 |
pre-seeding world means 'emerge -C package' gets rid of it, the |
| 26 |
@profile idea makes it completely different to uninstall it |
Archives