1 |
thanks |
2 |
|
3 |
previously jabberd2 is being merged from my own overlay too |
4 |
|
5 |
in /var/lib/layman/myown, I just make the directory net-im/jabberd2/, there |
6 |
is no other things in /var/lib/layman/myown |
7 |
|
8 |
Should I add some other things to the directory of my own overlay?? |
9 |
|
10 |
|
11 |
Did you previously rename your repo or pass PORTDIR_OVERLAY from the |
12 |
command line (which can sometimes confuse portage). |
13 |
=== |
14 |
No, i didn't do anything like that |
15 |
|
16 |
2010/6/29 Albert Hopkins <marduk@×××××××××××.org> |
17 |
|
18 |
> On Tue, 2010-06-29 at 19:51 +0800, Chen Huan wrote: |
19 |
> > I had done some hack on jabberd2, and I make a new ebuild for it, To |
20 |
> > avoid |
21 |
> > the new ebuild being overwrite when I execute "emerge --sync", I make |
22 |
> > /var/lib/layman/myown for this ebuild |
23 |
> > |
24 |
> > when I emerged jabberd2, it's normal, but when I try to re-merge it, |
25 |
> > the |
26 |
> > output is : |
27 |
> > |
28 |
> > Calculating dependencies... done! |
29 |
> > [ebuild R ] net-im/jabberd2-2.2.8 USE="berkdb ldap mysql pam ssl |
30 |
> > zlib |
31 |
> > -debug -memdebug -postgres -sqlite" 0 kB [?=>1] |
32 |
> > |
33 |
> > Total: 1 package (1 reinstall), Size of downloads: 0 kB |
34 |
> > Portage tree and overlays: |
35 |
> > [0] /usr/portage |
36 |
> > [1] /var/lib/layman/myown |
37 |
> > [?] indicates that the source repository could not be determined |
38 |
> |
39 |
> It's saying jabberd is being rebuilt, and orginally it was build from a |
40 |
> repo that is ownknown, and now it will be built |
41 |
> from /usr/lib/layman/myown. |
42 |
> |
43 |
> Did you previously rename your repo or pass PORTDIR_OVERLAY from the |
44 |
> command line (which can sometimes confuse portage). |
45 |
> |
46 |
> |
47 |
> |
48 |
> |