Bugzilla Bug 102810

Hello,

although I have left Gentoo as a developer half a year ago, I am writing this to
clarify some things I recently found in the ChangeLog.


  pnet-0.6.10.ebuild, pnet-0.6.12.ebuild, pnet-0.7.0.ebuild:
  We seem to have yet another unfortunate incident of
  keyword-happy developer.
  > Yeah, I am sorry for letting people test this package on different
  > architectures, I forgot x86 is the one and only


  There have been numerous instances of untested unapproved packages being
  keyworded, this was discussed time and again, the
  issue is mentioned in developer documentation,
  added to developer quiz, and voila, we have it again..
  > I have been a Gentoo developer for more than 2 years and
  > thus, I never took the quiz, but that just a side note to
  > satisfy your comment :)
  

  This time multiple packages in dev-dotnet/ category
  were marked as mips, ~mips, sparc, ~sparc, as well as
  working on other arches. It was confirmed that dotnet
  doesn't even build on most of these, yet they were
  keyworded.
  > LOL, this is pure FUD, let me tell you a few things:
  > There is no such package "dotnet", mono is *not* the same as pnet or
  > some variant of it, completly different codebase, but I take it, this
  > was probably just a typo.
  > 1. It was "weeve" from the sparc team who initially added the
  > sparc keyword, so I *heavily* doubt it's known to not work on sparc!
  > Also, I had access to gustavoz sparc developer box and it worked fine
  > there and also on the sparc boxes of other people I asked.
  > 2. It is known to work on mips, I even stayes in #gentoo-mips to
  > find people to test this and all told me that it worked (I had
  > only access to one mips box at that time).
  > 3. In the official Debian repository (you can check this on
  > packages.debian.org) pnet is available for the following platforms:
  >
  > alpha amd64 arm hppa hurd-i386 i386 ia64 mips mipsel powerpc s390 sparc
  >
  > so, PLEASE stop spreading FUD like "it is known not to work on those
  > architectures" or similar nonsense. And I might remind you that I once
  > asked you for access to your mips box (which was listed as a gentoo
  > developer box) and you denied access because you thought "GNU shouldn't
  > be wasting time with stuff like that" - very good idea to get Gentoo
  > moving forward that way ...


  Oh well... There seems to be no way to teach some people.
  > Yeah, thought the same when I read your ChangeLog entry.
 
 
  Removing mips and sparc keywords
  > OK.


Well, it is true that there were some platform-specific problems but they will
always remain and they were related to build foo (i.e. auto* stuff etc.) and
*not* C code that doesn't work on that arch, so you could have easily figured
out how to make it work on your box. Also you should remember that in Gentoo the
build chain changes dramatically over time and may cause problems with stuff
that was released a year ago, but see above.

I think you should remove/change that ChangeLog entry or at least write a follow
up that you don't like this software and started spreading FUD because of that.

Anyway, 0.7.2 was released a few hours ago, I just updated the GNU website etc.
and I hope Gentoo can get it working on the architectures mentioned above, just
like all the other distributions do, too.

Michael, could we get this bumped? 

Thanks!

Created an attachment (id=75127) [details]
pnet-0.7.2.ebuild

Version bumped and tested.

Created an attachment (id=75128) [details]
pnetlib-0.7.2.ebuild

Version bumped and tested.

Created an attachment (id=75129) [details]
0.7.2-resgen.patch (for pnetlib)

Bumped + Tested...

All latexer, all yours!

Commited to portage, sorry for the delay.