1 |
On 08/09/2013 12:09, gevisz wrote: |
2 |
> 2013/9/7 Marc Stürmer <mail@×××××××××××××.de <mailto:mail@×××××××××××××.de>> |
3 |
> |
4 |
> Am 06.09.2013 21:47, schrieb Paul Hartman: |
5 |
> |
6 |
> On Fri, Sep 6, 2013 at 2:28 PM, gevisz <gevisz@×××××.com |
7 |
> <mailto:gevisz@×××××.com>> wrote: |
8 |
> |
9 |
> But I have not found MATE in portage... |
10 |
> |
11 |
> |
12 |
> I see there is a mate overlay available in layman |
13 |
> |
14 |
> |
15 |
> layman -a mate |
16 |
> |
17 |
> |
18 |
> Thank you for the hint. |
19 |
> |
20 |
> I still have to learn how to use overlays... |
21 |
|
22 |
emerge layman |
23 |
[follow elog instructions on what to do with make.conf |
24 |
layman -L |
25 |
[pick the overlay you want |
26 |
layman -a <overlay_you_want> |
27 |
|
28 |
|
29 |
> |
30 |
> ... because I still need an omegaT (that is absent from portage) |
31 |
> and Skype (that is masked). |
32 |
|
33 |
Put ebuilds for them in your local overlay. It's not the same thing as |
34 |
layman - local overlay is just a directory with ebuilds you maintain |
35 |
yourself, tell portage where it is and it treats those ebuilds like they |
36 |
are in the main tree. it's fully documented in the portage docs |
37 |
|
38 |
|
39 |
> Is it safe to use packages from overlays? |
40 |
|
41 |
Depends. Is it safe to install software? An overlay is just ebuilds that |
42 |
fetches and builds software. may it's useful, maybe it's malware, maybe |
43 |
it's buggy, maybe it's not. |
44 |
|
45 |
If you real question is "Is there some official QA applied to overlays?" |
46 |
the answer is no. You either need to trust the overlay maintainer, or do |
47 |
the QA yourself. |
48 |
|
49 |
|
50 |
> Is there any ways to cleanly uninstall packages installed from overlays? |
51 |
|
52 |
Same as any other package: |
53 |
|
54 |
emerge -C |
55 |
|
56 |
|
57 |
To remove an installed overlay: |
58 |
|
59 |
layman -d <overlay_name> |
60 |
|
61 |
That just removes a tree of ebuilds. Portage tells you what is now out |
62 |
of sync with the next "emerge -uND world" |
63 |
|
64 |
|
65 |
-- |
66 |
Alan McKinnon |
67 |
alan.mckinnon@×××××.com |