Stan package for ArchLinux

[Ido Rosen]

Hi guys,
I'm trying to update the Stan package I made for ArchLinux. (I'm
also happy to make packages for other distros, like RPM, DEB, Ebuild,
etc.) Do I now need to have both the stan git repo and the cmdstan
git repo to get stanc working?

Also, do we have up to date build instructions for libstan, stanc,
rstan, pystan, etc. currently?

(Packages make it easy for non-dev users to just install and start using stan.)

Ido

[Allen B. Riddell]

Hi Ido,

Thanks! Getting Stan into a package on any one of those systems would be
a tremendous contribution. I looked into building a DEB package awhile
back. The main challenge is using the system libraries rather than
Stan's own copies of Boost and Eigen.

Thanks,

-a

> --
> You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Ido Rosen]

I got Stan packaged for ArchLinux already back in v1.3.0, just trying
to update it to v2.5.0 this week. If you don't care about it being
accepted into the main Debian or Ubuntu repository, then we can use
the Stan-provided Boost and Eigen and install it into /opt/stan/ for
example. Can host an Ubuntu PPA and Debian .deb packages to make it
easier for users of those distros to use stan.

[Allen B. Riddell]

Hi Ido,

I think it would be great to get Stan and CmdStan into the official
Debian (and Ubuntu) repository. But perhaps it wouldn't help non-dev
users as much as I think it would.

Maybe the next time someone does a Stan talk they could hand out a
survey (or ask for a raise of hands) about platform (Linux/Windows/PC)
and, for Linux, distribution (Ubuntu, Debian, Redhat, Arch, other).

Best,

[Ido Rosen]

Most likely it matters more what university/various academic and
corporate sysadmins are using on their compute farms and servers. In
that case, we already can assume Debian and RedHat are mandatory.

All of these distributions (RedHat, Debian, Ubuntu, Arch, Gentoo,
etc.) have third party repositories (e.g. EPEL/ElRepo for RedHat, AUR
for Arch, various overlays for Gentoo, various user-PPAs for Ubuntu
(stan should have one)). I was thinking we would just create third
party repos (I have some VM infrastructure for doing this already for
another project) that updates from the GitHub repositories any time a
new release is tagged. This could go into Jenkins or just a
web/service hook from GitHub.

Anyhow, I'll think about this over the weekend and try to put
something together. If anyone has packages for existing distributions
already made, please send them to me for inclusion. It'll save me
some time testing. For now, I have an Arch package that I'll update
to 2.5.0 sometime this week, an RPM forthcoming next weekend, and
ubuntu/debian DEB and gentoo EBuilds sometime in early Feb.

[Bob Carpenter]

We're moving away from libstan to a fully header-only approach
for the models in Stan 2.6.

Yes, all the instructions for everything should be up to
date. You can find them all starting from http://mc-stan.org

As to versions of Boost and Eigen, we should be compatible
with most of the recent versions of either. It's easy to specify
using different libs in the makefile.

- Bob