Chen Huan writes:
> I had done some hack on jabberd2, and I make a new ebuild for it, To
> avoid the new ebuild being overwrite when I execute "emerge --sync", I
> make /var/lib/layman/myown for this ebuild
>
> when I emerged jabberd2, it's normal, but when I try to re-merge it,
> the output is :
>
> Calculating dependencies... done!
> [ebuild R ] net-im/jabberd2-2.2.8 USE="berkdb ldap mysql pam ssl
> zlib -debug -memdebug -postgres -sqlite" 0 kB [?=>1]
>
> Total: 1 package (1 reinstall), Size of downloads: 0 kB
> Portage tree and overlays:
> [0] /usr/portage
> [1] /var/lib/layman/myown
> [?] indicates that the source repository could not be determined
>
>
> It says the jabberd2 's source repository could not be determined
>
> I know it is not a problem and can be ignored, but I want to know where
> I should modify to fix it?
The usual way would be to put it into the local overlay which is defined
by the PORTDIR_OVERLAY setting in /etc/make.conf. In order to avoid
another warning message, create a directory 'profile' there with a file
'repo_name' containing an arbitrary name, like 'my local portage tree'.
Wonko
