from /usr/portage/profiles/packages.mask # Diego Petten
from /usr/portage/profiles/packages.mask # Diego Pettenò <flameeyes@gentoo.org> (22 Aug 2005) w <lostlogic@lostlogicx.com> (29 Aug 2005) # Masked because it needs java 1.5 net-im/jive-messenger net-im/wildfire
Wildfire SHOULD not be unmasked. Wildfire does not adhere to generation 2 Java packages on Gentoo Java. 1.5 is only safe to use with generation 2 packages. Packages should no adopt 1.5 support before generation 2 was even in portage. Now that generation 2 is in ~arch. This ebuild either needs to be updated, or transferred to the Java herd. https://svn.gentooexperimental.org/svn/java/migration/docs/java-devel.html The ebuilds that are masked and in portage DO NOT compile with the new java system that is not masked but is only in ~arch at this time.
Should this be closed as a dupe of bug #120513 ?
The link posted is broken. Can someone please draw for me in crayon why Wildfire is so broken? I can accept that something is wrong with the ebuild. That said, this product kicks a**. I have uused jabberd a lot (regrettably). I just used a script found (http://micke.hallendal.net/archives/2006/06/migrating_to_wi_1.html here) to migrate to wildfire from jabberd. It grabbed my rosters, etc. It was amazing. This is a solid, easy to use, well packaged install. The main thing is: it works out of the box. It doesn't have a complicated evil XML file to config. It has a simple one, and everything else is web based. It's something that I can turn over with confidence to other admins. So, please, can someone point me to what is neede to make this "generation 2" compliant? sincerely,
a few hours later, this looks quite arrogent. My point wasn't to be an ass, it was to note that I fail to grok what needs to change, and i was hoping to see a simple (e.g. crayon) explaination of what/how to fix.
Can the java team please report on what is worng with the wildfire-3.1.0 ebuild? As far as I can tell it is generation 2 complient.
I'm also wondering why it still masked. The 4 month old comment about not compiling is hard to understand, as wildfire installed just fine after adding to /etc/portage/package.unmask and no other change to my java configuration.
I think the problem is that no one cares. No java devs certainly. Only the vague recommendations to read a broken webpage. I think that they are a great bunch of guys, but this project is not interesting. Wildfire 3.1.1 is in Asylumware portage (https://embassy.asylumware.com/projects/portage) It works, and so, if you want, please install gensync-dev, grab the asylumware.syncsource.
FYI: I unmask stuff, so if that's a problem, send me an email
The java-devel url has, obviously, since moved. It's available at http://www.gentoo.org/proj/en/java/java-devel.xml As for the ebuild, there don't seem to be any issues that I see with it. Lastly, we (Java team) don't maintain this particular package. Gustavo (humpback) does, so it is up to him to take care of unmasking.
(In reply to comment #9) > The java-devel url has, obviously, since moved. It's available at > http://www.gentoo.org/proj/en/java/java-devel.xml > Thanks for the link. > As for the ebuild, there don't seem to be any issues that I see with it. > Excellent! > Lastly, we (Java team) don't maintain this particular package. Gustavo > (humpback) does, so it is up to him to take care of unmasking. That's smashing - and without the second statment we still only have comment #1 to go by. So thanks for posting. Gustavo? Is this suitable for you?
(In reply to comment #9) > The java-devel url has, obviously, since moved. It's available at > http://www.gentoo.org/proj/en/java/java-devel.xml > > As for the ebuild, there don't seem to be any issues that I see with it. > > Lastly, we (Java team) don't maintain this particular package. Gustavo > (humpback) does, so it is up to him to take care of unmasking. > In the first comment It is stated by wltjr that this package did not conform to the java2 standard. As at the time this was a work in progress I requested some comments from the java team. I did not receive none, and I'm no java herd member so I waited. As the java team is very picky with the handling of java packages at the time I thought I was doing the correct thing. So please next time some java package does not comply to the standards please don't come bitching. I'll unmask it in a few minutes.
No need to get snippy about it. I recall we worked together on getting the 3.1.0 bump, and fixing up other issues wrt our Java policies, and that was some time after William's comment. I'm not sure why we didn't unmask it at that time... it must have been an oversight on both our parts. So, if this happens again where a lot of time goes by waiting to hear back from us or whatever, please just bump the bug, or try contact one of us on irc. Hopefully, we can avoid this kind of thing in the future....
Yay for team work!
