Critique my ebuild?

Discussions & Opinions
1

I need openconnect but the latest version 4.07 is unavailable. Here’s how I built an ebuild for version 4.07 based on Gentoo’s 3.11 version ebuild. Could it have been done better?

echo "PORTDIR_OVERLAY=/usr/local/portage" >> /etc/make.conf
mkdir -p /usr/local/portage/profiles/ /usr/local/portage/net-misc
echo "myrepo" >> /usr/local/portage/profiles/repo_name
cd /usr/local/portage/net-misc
cp -a /usr/portage/net-misc/openconnect ./
emerge --unmerge openconnect
cd openconnect/
mv openconnect-3.11.ebuild openconnect-4.07.ebuild
sed -i 's|3.11|4.07|' openconnect-4.07.ebuild
ebuild openconnect-4.07.ebuild digest
emerge openconnect-4.07.ebuild

I did receive a warning

*** emerging by path is broken and may not always work!!!

but it seems to have been OK in this instance. How should I point emerge to my ebuild?

2

This is ok.

In last line you emerge ebuild directly, but after you add own local overlay you can just <<emerge =openconnect-4.07>> not from <</usr/local/portage/net-misc/openconnect/>> dir

3

Thank you Yuri for your reponse. I was missing the = in my emerge command!
Also had to add an ACCEPT_KEYWORDS value to make.conf:

emerge =openconnect-4.07

Local copy of remote index is up-to-date and will be used.
Calculating dependencies... done!

!!! All ebuilds that could satisfy "=openconnect-4.07" have been masked.
!!! One of the following masked packages is required to complete your request:
- net-misc/openconnect-4.07::myrepo (masked by: ~amd64 keyword)


echo ACCEPT_KEYWORDS="~amd64" >> /etc/make.conf
emerge =openconnect-4.07