Package Details: slic3r-git a-21

Git Clone URL: https://aur.archlinux.org/slic3r-git.git (read-only, click to copy)
Package Base: slic3r-git
Description: Slic3r is an STL-to-GCODE translator for RepRap 3D printers, aiming to be a modern and fast alternative to Skeinforge.
Upstream URL: http://slic3r.org/
Licenses: GPL
Conflicts: slic3r, slic3r-xs, slic3r-xs-git
Provides: slic3r, slic3r-xs, slic3r-xs-git
Submitter: swiftgeek
Maintainer: swiftgeek (nickoe)
Last Packager: swiftgeek
Votes: 20
Popularity: 0.000000
First Submitted: 2012-06-23 10:45 (UTC)
Last Updated: 2022-06-03 17:50 (UTC)

Dependencies (27)

Required by (1)

Sources (3)

Pinned Comments

swiftgeek commented on 2016-04-19 00:37 (UTC) (edited on 2018-11-07 01:46 (UTC) by swiftgeek)

If something breaks on PKGBUILD side, please bother me directly on freenode (usually available at #slic3r) XS compilation requires more than 512MiB of installed RAM, adding same amount of swap makes it build (tested on armv7h, Allwinner A13)

Perl update guide: https://lists.archlinux.org/pipermail/arch-dev-public/2015-June/027236.html

or since 5.26:

pacman -Qqo '/usr/lib/perl5/5.26' where 5.26 is OLD version of perl

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 10 Next › Last »

swiftgeek commented on 2015-01-04 05:35 (UTC)

Quick reminder - whenever you recompile perl-wx, recompile perl-wx-glcanvas too (no need to recompile slic3r though)

pzl commented on 2015-01-02 16:26 (UTC)

two things I currently have to do to get master (69da8b0) to build correctly: 1: I installed perl-threads-aur 2: I added another sed line to the PKGBUILD, just below the others, to remove the line that parrots out the "threads.pm >= 1.96 required" warning. ( sed -i '/^\s*warn \"threads\.pm/d' ./lib/Slic3r.pm ) There seems to be a logic problem in lib/Slic3r.pm that makes this warning print out no matter what. I believe I have the threads dependency satisfied, but the warning prints out anyway, and disturbs the version number checking, which leads to a corrupt package. The warning had to be silenced for makepkg to build correctly, and end up with a tar package that didn't have the warning itself in the filename. Here's a small gist I created that prints each of the tests used in the Slic3r check before it prints the warning: https://gist.github.com/pzl/b53064b335457c417dbd If anyone else can shed some light on what's wrong here, I'd love to hear. I'm not too familiar with perl

swiftgeek commented on 2014-11-09 20:49 (UTC)

My packages are quite different - if human user is detected it provides means to configure package by `dialog` ways, as human interaction opt-in. Otherwise behaves like any other PKGBUILD or guesstimates configuration :] Interactive is needed when dealing with software in weird licenses (like nvidia installer sh/binary bundle - accept license to unpack image; requiring in license conscious agreement to license) Sorry for assuming that you were not ok with missing interactivity. And ofc thanks for semi-pointing out missing way to change commit/branch from PKGBUILD itself

pzl commented on 2014-11-09 19:38 (UTC)

"Pacaur is ... aiming at speed and simplicity, designed to minimize user prompt interaction" -- I believe this is a design decision. I'm also fine with non-interactive package installation. A google for "aur interactive pkgbuild" gives this forum link as the first result: https://bbs.archlinux.org/viewtopic.php?id=141372 which discourages interactive pkgbuilds anyway. it's easy enough to just edit the pkgbuild, so that's why I left the note for people who edit as well (I didn't realize other AUR helpers accept interactive prompts)

swiftgeek commented on 2014-11-04 16:50 (UTC)

I would consider it as a wrapper bug - tty responds with "not a tty" - which clearly isn't the case as you are using terminal (yaourt responds there with value from which was spawned eg. /dev/pts/5) Seriously, this is a huge bug - one of the easiest way to debug (or create package one-time-only) is to insert `bash -i` inside package/build etc pacaur/cower just floods std input with "Y"... That's retarded

pzl commented on 2014-11-04 15:49 (UTC)

I use pacaur as an AUR helper, it skips interactive mode entirely

swiftgeek commented on 2014-10-29 18:44 (UTC)

Interactive works everywhere (tested with yaourt/standalone) [if not describe bug] TODO: Make sure to not break "fragment" in source line I introduced _gitfragment variable (line ~36) to pass either branch or commit (I have to make it work with fragment vcs nicely)

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 10 Next › Last »