hi, i would like to see a psybnc ebuild, it would be lovely
Created attachment 30943 [details] Ebuild for latest PsyBNC Hello, I have created an ebuild for the latest PsyBNC, I also attached a patch that makes the install non-interactive. Please try it out, it is only my second ebuild, so comments and suggestions are welcome! PsyBNC is a multi-user and multi-server gateway to IRC networks, so I suggest net-irc. Arno
Created attachment 30944 [details, diff] Patch to make the ebuild non-interactive Patch to make the ebuild non-interactive
Created attachment 30945 [details] Init script for psybnc
Created attachment 30946 [details] Default config file for psybnc The patch, psybnc.conf and psybnc.initd go into /files
i have some suggestions: - latest version is 2.3.2-4 (see http://www.psychoid.net/) - install dir should not be /usr/local/psybnc/, as it is sometimes used for non portage stuff or nfs mounts. - you should use the +ssl USE flag to enable ssl and certificates creation: psybnc can run well without ssl support.
new patch for compiling with gcc 3.4
Created attachment 33795 [details, diff] patch for gcc 3.4 This patch contains the previous patch, and adds gcc 3.4 support :)
Created attachment 33812 [details, diff] gcc 3.4 patch (fixed) Contains the same as my last patch, but forgot something.
I'm trying to improve this ebuild, but I'm also facing some annoying problems. Following dju's suggestions I wanted to add the ssl use flag but if you have a closer, you'll notice that psybnc's static Makefile compiles autoconf.c, which checks the capabilities of the system (like ssl, ipv6, ...). You can't tune your configuration by adding a simple option like --disable-ssl - it needs editing the config.h, or using the menuconfig. To disable ssl support, you have to set the SSLPATH variable in the config.h to /dev/null (or somethnig else that doesn't reflect your real ssl path). Worse, it's even impossible to disable ipv6 support if you don't want it because there is no ipv6 variable into the config.h. So.. have you got ideas? I also noticed that the ebuild posted by Arno uses a "dirty" patch to generate a ssl certificate but now, there is another way to generate self-signed certificates. ssl-cert.eclass is made for this purpose. Then I also think that the install dir shouldn't be /usr/local/psybnc/ for the same raisons as dju` ones. Finally, do you really think it's necessary to create a special user/group for it? It's just my suggestions... it would be nice to see psybnc into portage one day.
Hey, I would like to see psybnc in portage too one day. How do you plan to do the trick with the salt.h. You need to copy it somewhere and let the ebuild use it, when compiling new version. Otherwise after an update the users won't be able to login anymore. Installing it under /usr/local/psybnc doesn't sound to good for me either. Why not put it into /opt/psybnc. Gentoo puts nearly everything there, so we would be in good company.
Changing the install path to /opt/psybnc is easy enough. The trick with this ebuild is to either make it non-interactive and complete or give some USE flags to it. Compile with all available options: Encryption/Blowfish, Translation, Internal Network, Traffic Logging, Linkage, DCC Files/Chat, Scripting, oidentd, Multinetwork support, & proxy support. Most of these are defaults. For those that aren't, config.h needs to be patched before make and the package must depend on oidentd. Add USE flags such as crypt, translator, etc to patch config.h quasi interactively. Also, we've got a version bump.
Created attachment 60234 [details] psyBNC-2.3.2-5 With some Flags This is a tar that will extract from /(ROOT) to /usr/local/portage/net-irc/psybnc Inside is the ebuild for the latest version. In this ebuild I've added the USE flags: - ssl - ipv6 - crypt - translate - partychannel
Comment on attachment 60234 [details] psyBNC-2.3.2-5 With some Flags This tar is worng
Created attachment 60235 [details] psyBNC-2.3.2-5 With some Flags tar will now extract to psybnc/
Created attachment 60236 [details] psyBNC-2.3.2-5 With some Flags Man... Now is the correct one....
Ok, it's really late here, and I don't want to add yet another tar... After untaring, inside the files dir, please rename: psybnc-2.3.2-5-partychannell-gentoo.diff to psybnc-2.3.2-5-partychannel-gentoo.diff I've tested, it builds...
After experiencing the issues myself I confirmed this with the psybnc dev team: psybnc does not play nice with >=sys-libs/glibc-2.3.4 glibc-2.3.3 seems the most recent stable build to support psyBNC-2.3.x A good reason why this isn't in portage.
Nice job Pedro! I have just 2 little remarks about your ebuild: 1- It doesn't seem to create any script in /etc/init.d/ 2- After emerging it, no configuration file seems to be created, is it normal? [ /opt/psybnc/psybnc.conf ]
psyBNC-2.3.2-6 has been released yesterday, more info on psybnc.info Pedro, could you try update your ebuild so we could test with >=sys-libs/glibc-2.3.4 ?
(In reply to comment #18) > Nice job Pedro! > > I have just 2 little remarks about your ebuild: > > 1- It doesn't seem to create any script in /etc/init.d/ > 2- After emerging it, no configuration file seems to be created, is it normal? [ > /opt/psybnc/psybnc.conf ] Well, that is strange co's on my system it creates the init script and also the .conf file. I'll update the ebuild for psyBNC-2.3.2-6 and double check those. I'll also be including: >=sys-libs/glibc-2.3.4 As Bols sugested...
(In reply to comment #18) > Nice job Pedro! > > I have just 2 little remarks about your ebuild: > > 1- It doesn't seem to create any script in /etc/init.d/ > 2- After emerging it, no configuration file seems to be created, is it normal? [ > /opt/psybnc/psybnc.conf ] After all, you were right, I dont think I included the init nor the conf on the previous tar. Also, the new ebuild will be for psyBNC-2.3.2-7 since this one is out...
is no one else experiencing problems with psybnc on >=glibc-2.3 ? Upstream devs tell me that it is not tested to work on anything above 2.2 and I can say from experience that I believe them. psybnc locks up intermittently on any of my gentoo systems running 2.3+
Created attachment 60869 [details] psyBNC-2.3.2-7.tar this tar will extract to psybnc/ Make sure you are on your overlay dir, under net-irc. If all is good you shall have the ebuild, init and conf files. Also this ebuld is now, as sugested: >=sys-libs/glibc-2.3.4 Have fun!!! P.S: Could anyone tell me how can I use this??? Can't seem to figure it out. Drop me a mail for that, pedro.algarvio@ufsoft.org, ;), I'm not joking...
(In reply to comment #22) > is no one else experiencing problems with psybnc on >=glibc-2.3 ? > Upstream devs tell me that it is not tested to work on anything above 2.2 and I > can say from experience that I believe them. > psybnc locks up intermittently on any of my gentoo systems running 2.3+ Mine doesn't lock, but I really can't tell all, because I can't figure out how to use it ;) I can connect to it!
http://www.psybnc.info/faq.html I should add that I use my bnc for multiple connection on multiple servers, both client and server connections using SSL. The process locks constantly when connecting to servers regardless of if it's an SSL server or not. If there was any debugging output I'd provide it.
Created attachment 73466 [details] Ebuild for lastest version -working with eutils- "inherit eutils" is included as first line enewgroup, enewuser, epatch does not work
Created attachment 85951 [details] init script (to be able to use oidentd) I ran into some problems trying to get oidentd to work with psyBNC. It turns out that the init script needed an update. This works with the latest version of psyBNC (2.3.2-7). I assume that you created a user psybnc:psybnc with the shell set to /bin/false. Create a file "psybnc" in /etc/conf.d/ and set USER="psybnc" and BNCPATH="/path/to/your/psybnc/" (or download the provided file and edit it).
Created attachment 85952 [details] conf.d file s.a.
Ebuild has been added to the gentoo sunrise overlay until I get my dev account updated with write access.
I will put it into portage when I get some time to do it, should be around monday (My first commit, so need to make sure I do everything correct)
I have commited it to portage now, marking as Fixed when the rsync servers catches up with it :-)
And it's online :-)
