First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 77636
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Net-Mail Packages <net-mail@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Gen Zhang <genneth@users.sourceforge.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
gmime-2.1.10.ebuild Ebuild for gmime-2.1.10 application/octet-stream Gen Zhang 2005-01-12 01:00 0000 1.48 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 77636 depends on: Show dependency tree
Bug 77636 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-01-12 01:00 0000 
New version of gmime, with mono bindings. Needed for Beagle. I have attached an
ebuild for it -- basically the same as 2.1.9, with new IUSE and one extra line
for econf. Built successfully on x86, so I've left that as the KEYWORD, whilst
changing the others to ~. If that's not the correct thing to do, please tell
me.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From Gen Zhang 2005-01-12 01:00:52 0000 ------- 
Created an attachment (id=48277) [edit]
Ebuild for gmime-2.1.10

------- Comment #2 From Andrej Kacian (RETIRED) 2005-01-12 04:49:30 0000 ------- 
Actually, our ebuild policy says that version bumps have to be marked unstable
on all keywords previous version had.

Moreover, there's a typo in provided ebuild - use_enabled instead of correct
use_enable.

That said, I'm testing the ebuild as we speak.

------- Comment #3 From Gen Zhang 2005-01-12 04:53:11 0000 ------- 
Ah, oops! It seems that the tarball does autodetection, so the fact that it
failed just meant that everything happened as expected... Thank you for
clearing up the KEYWORD problem.

------- Comment #4 From Andrej Kacian (RETIRED) 2005-01-12 05:21:53 0000 ------- 
Ok, found another bug - gmime also needs gtk-sharp installed:

checking for gtk-sharp >= 0.91.1... Package gtk-sharp was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtk-sharp.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtk-sharp' found

When determining dependencies for a package, it is a good idea to look in configure.in (or .ac).

------- Comment #5 From Gen Zhang 2005-01-12 05:24:14 0000 ------- 
Ah, good pointer. I'll remember that.

------- Comment #6 From Andrej Kacian (RETIRED) 2005-01-12 05:28:42 0000 ------- 
Hm, and as dev-dotnet/gtk-sharp doesn't have any amd64 keyword, we'll have to
drop amd64 from gmime for the time being. I'll fill a bug to amd64 team to test
these packages and add their keyword as appropriate.

------- Comment #7 From Andrej Kacian (RETIRED) 2005-01-12 05:47:26 0000 ------- 
InCVS now, thanks for the ebuild.
First Last Prev Next    No search results available      Search page      Enter new bug