Summary: | add mail-notification ebuild to portage | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | alex f <acid.punk> |
Component: | New packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | amd64, desktop-dock, jbilbo, obz |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.nongnu.org/mailnotify/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 57197 | ||
Bug Blocks: | |||
Attachments: |
mail-notification-0.5.0.ebuild
mail-notification-0.5.0.ebuild mail-notification-0.6.1.ebuild mail-notification-0.6.2.ebuild mail-notification-0.7.1.ebuild |
Description
alex f
2004-07-27 05:59:01 UTC
Created attachment 36257 [details]
mail-notification-0.5.0.ebuild
This adds some new local use flags:
gmail - add support for google's gmail
mh - add support for mh mail
pop3 - add support for pop3 mail accounts
sylpheed - add support for sylpheed mailboxes
Just some stylistic notes on the ebuild, for when you're using the gnome2 eclass: 1.) use G2CONF rather than overriding src_compile() { } eg G2CONF="${G2CONF} `use_enable mbox`" G2CONF="${G2CONF} `use_enable pop3`" etc 2.) do you need to add pkg-config to the DEPEND's? Created attachment 37138 [details]
mail-notification-0.5.0.ebuild
* removed some useflags, as they don't add any DEPEND's so it's only pop3 and
gmail now
* changed src_compile() to G2CONF
About pkg-config, yes it's needed, but it get's included with the gnome-panel
dependency for example.
Created attachment 37950 [details]
mail-notification-0.6.1.ebuild
Upstream released a new version. This removes the gnet dependency, introduces
gob-2 as new dependency. Only new local useflag now is gmail.
when I install the ebuild, it compiles fine but at runtime I get the following: A fatal error has occurred in Mail Notification Bonobo could not locate the GNOME_MailNotification_Automation.server file. Please check your Mail Notification installation. On http://www.nongnu.org/mailnotify/ , a solution is given. Should this be implemented in the ebuild? If you need any more info, just post back. Thanks. If I run Applications/Internet/Mail Notification and configure mail-notification, there is no error and the application runs as expected. The upstream solution for comment #5 is to install mail-notification into the same path as Gnome. That's already the case. But it seems like you have to restart your X11/Gnome session after merging mail-notification. What else has to happen for this to be in portage? How can I help? In CVS now, it'll be on the rsync mirrors in an hour or two. Thanks for reporting. Just as a note - I removed the gmail USE flag from the ebuild. The automatic checking/retrieval seems to violate Gmail Terms of Use, Section 5. If this is found to not be the case, feel free to reopen the bug/mail me/shout at me very loudly. In the meantime, better safe than sorry. Well, Google themself provides a systray application for Gmail, just not for linux. I also never heard that somebody lost his account because he used such an application. And none of the authors of the many Gmail checking applications out there have received mail from Google asking them to stop. Not that I'm aware of. So there aren't any signs of Googles disapprovement. I see you have stripped the DESCRIPTION of the many supported formats and methods. I listed them so that when people emerge -s something this app would turn up. Please add them back. By the way you say you've removed Gmail support from the ebuild, yet Gmail is the only thing you have left in the DESCRIPTION. re comment #10: Is this the line you're referring to in part 5? "You also agree that you will not use any robot, spider, other automated device, or manual process to monitor or copy any content from the Service. The Google Rights include rights to (i) the Service developed and provided by Google; and (ii) all software associated with the Service. The Google Rights do not include third-party content used as part of Service, including the content of communications appearing on the Service." IANAL, but it says that you can't use any "manual process" or "automated device" to "monitor ... content from the Service". I think they're talking about the actual content of the site (i.e., the site logo and layout) instead of the emails that are transmitted. Otherwise, logging in and checking your mail could constitute a manual process to monitor content. Also, later in part 5 the TOS states that "The Google Rights do not include...the content of communications appearing on the Service". I would contend that the email itself has content, as well as the body of the email. Examples of this are blank emails sent from cronjobs, etc. If you receive an email at a certain time, thats content right there. For example, if I get an email at 7:00am, I know that I have to run emerge world to update my system. Finally, "The Google Rights do not include third-party content used as part of Service, including the content of communications appearing on the Service." It just says including, but doesn't say that the third party content is limited to emails. Could mail-notify constitute third-party content? There are also some technical reasons to question whether or not its okay to have a gmail monitor. The ads only show when you actually read the emails, and there is no technical difference between mail-notify and the gmail checker (at least from a network standpoint, I think [can someone verify this?]). Just my $0.02. We can speculate about this as long as we desire, but I wouldn't recommend enabling gmail support for mail-notification until Google expresses their official standing on this, which should happen soon, what with increasing use of libgmail and gmailfs (I know that mail-notification is different to gmailfs, but still). See bug #62100 for similar issue. Comment #14, what makes you think that Google is going to "express their official standing on this" to "happen soon"? Did you ask Google? Aside from the Gmail issue -- Tom, so how about putting back the original DESCRIPTION because of Comment #12? Created attachment 39244 [details]
mail-notification-0.6.2.ebuild
Upstream released a new version. It seems the 64bit patch isn't needed anymore,
so I removed that from the ebuild. Also I changed the DESCRIPTION back. It
really isn't that much longer than the DESCRIPTION of the ebuild already in the
tree, but is IMHO so much more useful. Please add it to the tree.
Thanks, in CVS now. I have removed ~amd64 keyword for now, to be sure. amd64: could you please test if the new version works fine on your arch without the patch needed for 0.6.1 ? Thanks. Re-marked ~amd64. Thanks for taking care of this Andrej :) Mail Notification 0.7.0 released Wednesday, October 6, 2004 New (optional) MIME support for mail-notification requires gmime package installed. Setting depend on a bug where an ebuild for gmime is being crafted. 0.7.0 in CVS now, along with newly added MIME support. Thanks for reporting! I have also removed ~amd64 from KEYWORDS, until gmime gets it. Bug for that is already filed. Mail Notification 0.7.1 released Created attachment 43020 [details]
mail-notification-0.7.1.ebuild
bump version and add gmail support via USE flag. Would be the 3rd gmail app in
portage.
Mail Notification 0.8.0 released Renaming the 0.7.1 ebuild which I posted yesterday will work for 0.8.0. The bump is in Portage now, but for reference, could all new version bump requests please be filed as new bugs. Thanks. Do I need any use flags turned on to get gmail support? |