Package Details: slic3r 1.3.0-20

Git Clone URL: https://aur.archlinux.org/slic3r.git (read-only, click to copy)
Package Base: slic3r
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/
Keywords: 3d-printing
Licenses: GPL
Conflicts: slic3r-git
Provides: slic3r
Submitter: nickoe
Maintainer: nickoe (swiftgeek)
Last Packager: nickoe
Votes: 53
Popularity: 0.000444
First Submitted: 2012-08-26 23:07 (UTC)
Last Updated: 2022-09-24 18:19 (UTC)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14

swiftgeek commented on 2012-10-23 06:39 (UTC)

With slic3r the git version is stable and tagged versions .... are just tagged ;]

nickoe commented on 2012-10-23 06:35 (UTC)

I have now updated the package according to ejona86's version of the PKGBUILD. I am happy that it now does not use a binary precompiled slic3r but a source tar. @swiftgeek I think it is nicer to have a dedicated "no-suffix" package, when you wan't a stable version of a program, hence I maintain this package. The -git package is still nice to have when I wan't to test new features. I like to have a PKGBUILD that I don't have to modify to get the stable/official latest version.

ejona86 commented on 2012-10-23 04:26 (UTC)

@swiftgeek. My PKGBUILD requires no modification to use a tag instead of master (thus, I think easier), is obvious which version is installed (-git PKGBUILDs don't tell you which commit the code was) (thus, again, easier), and is fewer lines of code because of no double "git cloning" and other git bits (cleaner). The tar.gz mine downloads is 512K; git clone downloads 2.81MB (less bandwidth). My PKGBUILD is "normal" in that it could also become part of community if it was popular enough. I have no issue with *-git PKGBUILDs, but I only want to use them if there is a bug in the current version of the package but fixed on master (or that new shiny feature just got added to master :-) ).

swiftgeek commented on 2012-10-23 02:56 (UTC)

but You can use git to download tagged branch... which seems to be way easier, cleaner and takes less bandwidth ;)

ejona86 commented on 2012-10-23 02:52 (UTC)

I disagree with swiftgeek, in that I don't want the git version. I do want the code built though (as is standard for PKGBUILDs of open-source components), and not using the binaries like this package is doing now. I adapted swiftgeek's git-based PKGBUILD for handling release tags (version 0.9.3): http://pastebin.com/Pgpfb3uu .

swiftgeek commented on 2012-09-06 11:25 (UTC)

There is no reason to use "stable" code - unless it's a package in official repo. Current GIT version is always better here. And use git even for the official package - there are tags in this repo. https://github.com/alexrj/Slic3r/tree/0.9.2

« First ‹ Previous 1 .. 9 10 11 12 13 14