I'm making an ssh.com ebuild...but....

[Petyr]

Like many other's I'm getting the access violation
I've traced it down to the makefile calling ssh-keygen which then tries to write to /root/.ssh2/random_seed
The man pages says that it does this based on $HOME/.ssh2/random_seed
The code doesn't quite do that... It's actually fairly smart. Resetting $HOME in the ebuild does not fool the program and it still tries to write to /root.
Needless to say portage says "Oh hell no" tosses an access violation and the install fails *sigh*
The next trick I guess I'd like to try is chroot the bastard, but I'm not sure if that will work correctly nor do I have an idea on how to do that in the first place.
Any suggestions?

Side note: I'm not entirely sure if ssh.com would allow an ebuild to be made so for now I'm just using it internally for their non-commercial license. Having an ebuild just makes my life as a sysadmin easier ^_~
I'll actually look into seeing if I could release it to the world after I get the darn thing working

Thanks in advance!

Petyr Rahl

[Pythonhead]

How about using sed to change the line in the Makefile?

[Petyr]

I think I'm going to do that actually because there doesn't appear to be anyway that I can force ssh-keygen to play nice. Therefore I'll just add a line in there for a person to do
ebuild <package> configure (I think that's it... doing this off the top of my head ^^;;; )
Thanks for the tip =)

Petyr Rahl