Gnubiff (http://gnubiff.sourceforge.net/) is a nice application for checking emails. I would like to install it via an gentoo ebuild. Could you please add an ebuild? Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 25904 [details] Initial ebuild It's incomplete I think. There's may be a lot of dependencies that might be missing or superfluous. I have a running Gnome system and the builds detects that. It will end up being available as a Gnome applet. To know if it will work for you, try it, it's kinda neat.
Created attachment 25905 [details] Oups! I made a booboo! I forgot to change the use variable value. Should be gnome not gtk2. Fixed now. Sorry for wasting 542 bytes.
Created attachment 29040 [details] gnubiff-1.0.10 Does not install properly. To be sure it was not due to gnome_src_compile, I replaced it with ./configure and change pkg-config with gnome-config. As such, i putted the ~x86 flag. I also added --with-password so that you don't have to enter them on each reboot.
Created attachment 29083 [details] gnubiff-1.0.10.ebuild Cleaned up my act. - The "`use gnome`" was (again) used the wrong way. Now it does use gnome2_src_compile if a gnome use flag is found. - Removed the use of gnome2_src_compile if no gnome use flag is found. It uses the conventional econf and emake instead. This is untested by me. If you do not want password saving, remove the --with-password. I put this into gnome-extra category.
Created attachment 38089 [details] gnome-extra/gnubiff-1.4.0.ebuild Upgraded the original ebuild: 1. Version bump to current version 1.4.0 2. changed archive type from tar.gz to tar.bz2 in the download URL to conform with archive type found on Sourceforge.net 3. added new configure option '--with-password-string' to utilize the improved security options in the upgraded build.
Added myself to cc list.
Three insights on the ebuild: 1. Header is missing from the ebuild (see http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3) 2. Did you really test on all architectures you included in KEYWORDS? 3. "src_compile()" is preferable to "src_compile ( )" Fix these and I'll add the ebuild to portage.
Now there's a new version anyway-- 2.0, released two days ago, September 1st-- and the many changes suggest a possibility that the ebuild would have to be completely rewritten to accommodate that: Changelog Version 2.0.0: * gnubiff now officially part of the GNU project * Complete redesign of interface inspired by MailNotification by Jean-Yves Lefort. * Automatic detection of mailbox format * Better handling of SSL certificate * New option to tell gnubiff to never send passwords in clear * Various small bugfixes * Security fix in possible buffer overflow (pop3.c) * Security fix in pop3 (infinite uidl list would block gnubiff and ultimately crashes it) * Bugfix in geometry handling (was not saved properly) * Bugfix in pop3 protocol to really get only most recent headers * Bugfix in apop protocol which was really broken * Bugfix in imap4 to handle server panic * Bugfix in utf8 translation * Added hidden files in gtk_file_chooser's I'm not sure if dependencies or USE flags have changed, but I'll investigate that further. The changes "inspired" by the Mail Notification applet makes that sound like a good idea, since I can easily speculate that the latter applet might have dependencies or flags that were previously not used in this one, but are now (due to the aforementioned inspiration). I didn't write the original ebuild, but since I don't know if the original author is around, I'll take a stab at trying to see what's what and fixing the ebuild for at least one of the versions (1.4.0 is working fine on my x86 machine, so hopefully I can fix that ebuild, and if I can write the new one, then I can upgrade, too). So, thanks for the links to ebuild writing how-tos-- I will definitely need them, having never done this before, but I'm always looking for a chance to learn something.
Great, feel free to email me directly if you need help writing that ebuild.
Created attachment 43317 [details] net-mail/gnubiff/gnubiff-2.0.2.ebuild I just wanted to give gnubiff a try and I wasn't able to find a more recent ebuild than the one offered here. So I took it as a base and tweaked it - looks good to me so far and heck, it actually compiled fine and works as expected. ^^
In CVS portage with minor modifications. Should be hitting mirrors in a few hours. Thanks for the ebuild, Andreas.
Created attachment 46922 [details] net-mail/gnubiff/gnubiff-2.1.0.ebuild Slightly modified version of gnubiff ebuild: Added new use flag for saving passwords within config file (USE="password") Because the password should be scrambled with a random string, I had to modify the DEPEND variable, too. However, this seems a bit excessive to me; any ideas how to get a random plaintext-password without utilising coreutils/sharutils?!
I'll have a look at this later today, hopefully.
I had to go back to version 1.4.0 to get a working gnubiff. All the more recent (including my orginal adapted to latest) gives error connecting to mail servers. I tried with and without password and password string. Now I think I also have broken gnome applet support for gnubiff because going backwark I probably ended up overwriting old on new in the Gnome's scribber (or whatever the hell it's called) and now any new installs never shows up in the Gnome's applets list. All of you guys got this working? I remember dropping Gnibiff because it's always unstable. Version numbers should have a 0. in front of them all.
Oh, and I'm adding myself for CC so that I DO GET NOTIFIED when someone ask me something.
Well, never mind my ranting post about this not working. I did not know why but it worked after I restarted the X session. So, i gues, probably just some gnome re-initialization is needed. Why the 1.4.0 version worked without any restart is maybe due to the fact that I used gnome2_src_compile in that ebuild to perform the build, I don't really know. Maybe it's gnubiff itself. A guru is needed to answer that one. Anyhow. It now works and all its bugs too.
ticho, can i take care of this package? (i'm in net-mail herd)
Yes, by all means, go ahead. Sorry for neglecting this, everyone. :/
Woohoo! One less thing to take care of. :D All go for me :)
Some ebuilds use $RANDOM as password like PASSWORD="${RANDOM}${RANDOM}${RANDOM}${RANDOM}". but it's only numeric. or, we might use app-admin/makepasswd but we need to add it to DEPEND. i prefer $RANDOM.. any idea?
Try both. Use your better judgment. We'll try it. For myself, I having trouble to remember what is this all about. It's for encrypting the passwords inside a file, right?
I already tried both :) I'm going to use $RANDOM unless there are any objections. > It's for encrypting the passwords inside a file, right? right. once you set password in gnubiff, you don't need to input password again.
ok. i've just added gnubiff-2.1.1.ebuild which use ${RANDOM} to the portage tree. please report if there are any problems.
I'm saying this lust like that, but why burn the step of publishing it into this bug before dissiminating potentialy broken software to Portage? Especially since you have people willing to test it from here first, I myself don't particularly appreciate when devs consideres me a ginea pig for alpha testing their ~x86 software by putting it into Portage which ends up replacing the perfectly working application on my system. I update my tree every sunday. So I will wait until next sunday to test your gnubiff and let the others struggle with it to determine if it works or not. Or, publish it here first.
I confirmed it's working. And it will be enabled only when you set USE="password". So, i don't thint it'll be big problem. And ~ARCH is suitable in this case because it's for testing purpose.
You confirm it's working, yet you anticipate problems by asking people to report them. Also, gnubiff (like many other packages for that matter) are ~x86 keyworded. I don't think it's suitable to try or test alpha things. Like I said, I'm saying it because I think it, not to be an ass for the fun of doing a reproach. Maybe this will work ok, but one day you'll be bound to publish something that will only work on your setup and not on some other. Nuf said about this ;)
> You confirm it's working, yet you anticipate problems by asking people to report them. Yes. I thought there might be problems in some enviroment. (everytime I think it) So, I added ~x86 masked gnubiff to the portage tree. from http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml. "KEYWORDS (snip) If the KEYWORDS flag has a preceding ~, then that indicates that the particular ebuild works, but needs to be tested in several environments before being moved to the stable profile with the given keyword."
