overlay, and ran into my first issue.
While running 'emerge -av binkd' I received this:
('Filesize does not match recorded size', 506625L, 506236)
this means that the tarball is not the same tarball i created the ebuild to, its being updated since :)
i will after this issue a new ebuild that works again, thanks for reporting
I knew what it meant. I just figured I'd let you know. :)
Of course. Anything I can do to help. And thank you for providing the overlay!
suggestions on /etc/conf.d/binkd and /etc/init.d/binkd why not just use /etc/xinet.d/binkp ?
i think about USE flags to enable disable things in configure, but also to n make it bloated with to much possilibies in not working config
suggestions on /etc/conf.d/binkd and /etc/init.d/binkd why not just use
Frankly, I've never looked into it. I don't run xinetd over here.
Though I did make a successful /etc/init.d/binkd using start-stop-daemon. It works, and I'm not thoroughly informed on ivp6 yet, so I really have no
reason to have that enabled. Honestly, I don't really know what it does or
how it works yet. But someday. :)_
i think about USE flags to enable disable things in configure, but also
to n make it bloated with to much possilibies in not working config
You could. But then again, I don't even use a "USE" variable in /etc/make.conf right now. I used to have one that was 1000 characters long
with a desktop environment.
I'm not really into that anymore.
The BBS machine is a nice new Gentoo install with syslog-ng, logrotate, vixie-cron, and a dhcp client. That's about it besides my prerequisites for my BBS software,
the software itself, and binkd. I'm trying to keep it minimal this time around. I have an i5 with multiple VMs for toying around with whatever I want.
Either way, the original binkd tarball compiles fine with no requirements,
USE flags, or anything else for that matter. And I'm totally fine with that. :)
|Location:||Riverside County, California|
|Nodes:||15 (0 / 15)|