<FFY00>
mithro, btw I am also interested in packaging the symbiflow toolchains
<FFY00>
but I think I am going to wait for a nextpnr release
<FFY00>
which itself is waiting on yosys
<mithro>
FFY00: My experience with distro packaging has been that someone does the packaging once and then the original packager gets busy and it ends up becoming super obsolete quickly
<FFY00>
mithro, which distros were those?
<FFY00>
by experience with debian based distros has not been great
<mithro>
FFY00: everything were I haven't also been the package maintainer or the distro doesn't package directly and automatically from git (Ubuntu, Debian, Fedora, SuSE, slackware, etc)
<FFY00>
IMO they overcomplicate packaging too much
<tpb>
Title: PKGBUILD « trunk - svntogit/community.git - Git clone of the 'community' repository (at git.archlinux.org)
<FFY00>
that's all you need to build it
<FFY00>
when it updates, just bump the pkgver and update the checksums (which can be automated) and build
<FFY00>
it's literally 2 commands in my terminal
<mithro>
FFY00: The packaging is never the problem -- the issue is keeping the packages rolling to the new versions
<FFY00>
but when the packaging itself is trivial it makes things work much better
<FFY00>
at least this has been my experience
<mithro>
FFY00: Generally what happens if that people get busy or move on to other things
<FFY00>
in arch, I might ask someone else to co-maintain the packages
<FFY00>
or to take over
<mithro>
FFY00: Places where packaging has worked okay is when there is a group of people assisted with automated systems
<FFY00>
if I am busy I can just hop on the irc channel and ask for people to update my packages
<FFY00>
in arch the building is automated
<FFY00>
but you still need to manually update it
<mithro>
FFY00: Debian has gotten a lot better now they have tooling that monitors upstream for releases and automatically creates bugs and nag emails when the package is behind
<FFY00>
by this I mean: it won't update automatically on an upstream release
<FFY00>
each packager in arch as its own way to monitor upstreams
<FFY00>
most use nvchecker
<FFY00>
but it works pretty well
<FFY00>
mithro, I hope that you'll have a good experience with arch :)
<FFY00>
I'll try to make it happen
<mithro>
FFY00: I would say that fpga toolchains and getting good cross compiler packages make more sense for packaging then the litex