FS#31498 - [mayavi] 4.2.0 doesn't work well with the current VTK

Attached to Project: Community Packages
Opened by Chen Xing (chenxing) - Tuesday, 11 September 2012, 19:11 GMT
Last edited by Andrzej Giniewicz (Giniu) - Saturday, 15 September 2012, 07:51 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Andrzej Giniewicz (Giniu)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi, thank you for moving Mayavi to [community]!

However, this patch is critical for Mayavi to work normally with the latest version of VTK:
https://github.com/enthought/mayavi/commit/e61d4afa02072b48a332c7250b293704f57c6b2a

Can you please include this patch in the package?

Besides, why is python2-mayavi-git removed from AUR?
This task depends upon

Closed by  Andrzej Giniewicz (Giniu)
Saturday, 15 September 2012, 07:51 GMT
Reason for closing:  Fixed
Comment by Jelle van der Waa (jelly) - Wednesday, 12 September 2012, 13:01 GMT
Git packages aren't recommended for packaging, we like to package stable releases.
Comment by Chen Xing (chenxing) - Saturday, 15 September 2012, 07:42 GMT
  • Field changed: Percent Complete (100% → 0%)
Not actually request re-open. I understand git is not good for [community], but it should be OK for AUR, right? Why not keep the package in AUR?
Comment by Andrzej Giniewicz (Giniu) - Saturday, 15 September 2012, 07:50 GMT
I removed those packages for a few reasons. It was long time ago when ETS did not compile on Arch, so I had to build from svn, later switched to git. When it became stable enough and released quite often, I orphaned them, because I had not need for them - and by design - I don't maintain packages I don't use at least from time to time, because I'm unable to catch errors.

It happened, that they were orphan for long months, with at most 1 vote, and most of them were broken or incorrect. As the state progressed, it is was now easier to make a new package, than to update old, broken packages.

So, if someone really needs git version, I recommend copying PKGBUILD of stable version from community, change it's name and source, add few extra lines from PKGBUILD git prototype and have a working version, instead of broken one. You are free to do this of course, and it would be far less work than bringing old ones up to par.

Loading...