Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38932 - [blender] Unstable versions are packaged

Attached to Project: Community Packages
Opened by gandalf3 (gandalf3) - Sunday, 16 February 2014, 06:16 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 20 February 2014, 18:16 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
It appears that unstable versions of Blender are being packaged.

There is a comment in the PKGBUILD about this:

"Sometimes blender.org takes some time to release patch releases and because Arch users
are impatient, we sometimes need to build from git directly."

Blender usually releases new versions every 8-12 weeks (source: http://wiki.blender.org/index.php/Dev:Doc/Process/Release_Cycle), which seems reasonable enough to me. From the point of view of an impatient Arch user, to have unstable versions installed alongside the stable version, I'd rather (a) build unstable versions myself or (b) use the "blender-git" package in the AUR.

The above paragraph implies that Arch only packages stable versions of Blender, which is not currently the case.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 20 February 2014, 18:16 GMT
Reason for closing:  Not a bug
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 17 February 2014, 22:20 GMT
Have you actually tried building Blender from the last stable release in an up to date Arch before you made this bug report? I would guess that you haven't since it doesn't actually work due to the dependencies breaking the build. Since we always roll all of Blender's dependencies, sometimes Blender fails to build and it only get fixed in a newer commit of it. There really is no fix against this as I don't see myself backporting lots of patches every now and then, I just bump the git commit and usually it works. If you think this is improper, suggest a better course of action. I'll leave this report open for discussion for a few days.
Comment by gandalf3 (gandalf3) - Tuesday, 18 February 2014, 07:47 GMT
That is a good point.

The only solution I can think of is packaging "portable" versions and dumping them in /opt, but that's further from proper if anything..
Maybe it could work as an AUR package.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 18 February 2014, 09:47 GMT
Making a subdistribution in /opt just for Blender is rather insane. I know that the current solution is not optimal but Arch is always about finding the most practical solution to a technical problem and I think I found it. Unless you have anything to add or any technical suggestions I'm going to close this soon.

Loading...