JimD wrote:
I am using net-misc/rinetd to forward port 443 to 22, 21 to 5900 and
8080 to 119 because those ports are blocked from work.
When I first installed rinetd, I noticed that amd64 was not in the
KEYWORDS. I added amd64 to the KEYWORDS in the ebuild and it has been
working fine. However everytime I run emerge to update world/system
I get the following warning:
[EMAIL PROTECTED] $ sudo emerge -vpuDN world
These are the packages that I would merge, in order:
Calculating world dependencies
!!! Packages for the following atoms are either all
!!! masked or don't exist:
net-misc/rinetd
I have net-misc/rinetd ~* in /etc/portage/package.keywords but that
doesn't seem to help.
Will I have to keep updating the ebuild after every emerge --sync?
Jim
If you leave it in /usr/portage, yes, because each --sync restores the
tree to being an exact mirror of the one on the sever. To work around
this, Portage supports "overlays" which allow you to keep your own
modified or custom ebuilds which won't get overwritten. You can
configure any number of overlays with the PORTDIR_OVERLAY setting in
/etc/make.conf. Set it to, for example,
PORTDIR_OVERLAY="/usr/local/portage" to place an overlay in that
directory. You can add additional overlays by separating them with
spaces. Within the overlay directory, you should arrange your ebuilds
the same way as they are in the original /usr/portage - for example,
your modified rinetd ebuild would go as
/usr/local/portage/net-misc/rinetd/rinetd-0.62.ebuild, assuming you're
using that version. emerge --sync won't overwrite your overlay. One
final step remains - to checksum your ebuild so that Portage can verify
it, you must run 'ebuild /path/to/ebuild digest' any time you modify
it. Portage won't use ebuilds or files that haven't been 'digested' in
this way. Once again assuming you're using rinetd-0.62 in an overlay at
/usr/local/portage, your command would be 'ebuild
/usr/local/portage/net-misc/rinetd/rinetd-0.62.ebuild digest'.
If you aren't having any problems running the package on your amd64, you
may want to search Bugzilla (http://bugs.gentoo.org) for the reason why
rinetd isn't keyworded for it, and perhaps file a bug requesting it to
be added.
HTH.
P.S.: If you add amd64 to the KEYWORDS in the ebuild in your overlay,
you shouldn't need to have a package.keywords entry for it at all, since
amd64 is the stable keyword.
--
[email protected] mailing list
