Skip to content

Instantly share code, notes, and snippets.

@luzpaz
Last active September 23, 2022 14:57
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save luzpaz/e9181162ac70f32429381909f58459a6 to your computer and use it in GitHub Desktop.
Save luzpaz/e9181162ac70f32429381909f58459a6 to your computer and use it in GitHub Desktop.
List of FreeCAD packagers (with accounts on Github)

Packagers

Packager Platform/Dist
@xyproto Arch
@adrianinsaval Arch AUR
@looooo Conda
@kkremitzki Debian/PPA
@hobbes1069 Fedora
@PrzemoF Fedora Copr
@waebbl gentoo
@adrianschroeter openSUSE
@ipatch macOS homebrew
@ppd Snap
@hfiguiere flatpak
@donovaly Windows LibPack
@apeltauer Windows LibPack
@sgrogan Windows
@moench-tegeder FreeBSD
@mandian OpenMandriva
Packager Platform/Dist Twitter
@xyproto Arch
@adrianinsaval Arch/AUR
Arch/AUR @Fabio_Lolix
@looooo Conda
@kkremitzki Debian/PPA @thekurtwk
@hobbes1069 Fedora
@PrzemoF Fedora Copr
[@waebbl][gentoo] gentoo
@adrianschroeter openSUSE
[@ipatch][homebrew] macOS homebrew
[@vejmarie][homebrew] macOS homebrew @vejmarie
@ppd Snap
@luzpaz Snap
[@hfiguiere][flatpak] flatpak @hfiguiere
@donovaly Windows LibPack
@apeltauer Windows LibPack
@sgrogan Windows
@moench-tegeder repo FreeBSD
FreeBSD @koobs
@mandian OpenMandriva

Notes

@adrianinsaval
Copy link

to be more specific about triggering a flatpak build, you would need to make a PR to that repo specifying the commit hash in the org.freecadweb.FreeCAD.yaml file. Also consider adding the link for the flatpak github repo
[flatpak]:https://github.com/flathub/org.freecadweb.FreeCAD

@luzpaz
Copy link
Author

luzpaz commented Jun 14, 2022

Added, Not sure why the wiki markup isn't working.

@adrianinsaval
Copy link

adrianinsaval commented Jun 15, 2022

If I'm not mistaken @xyproto and @svenstaro are maintainers for the official archlinux package, can you guys confirm? How can we contact you regarding freecad packaging? I've sent emails to what I believe to be your addresses but I don't know if that's the best method.

@svenstaro
Copy link

I'm not a freecad maintainer, I just sometimes have to rebuild it by I'm really not involved in anything beyond trivial rebuilds.

@xyproto
Copy link

xyproto commented Jun 15, 2022

@adrianinsaval Hi!

If there is a problem with the packaging, https://bugs.archlinux.org is a good approach, because it's easy to transfer tickets between maintainers, if needed.

If it's about updating the freecad package, the "flag out-of-date" link at the package page works.

I have been traveling in connection with work and also have new signing keys, so several of the packages I maintain currently need a checkup.

Update: The freecad package should be in good shape now.

@adrianinsaval
Copy link

I'm trying to contribute to the PKGBUILD actually since there is a few things that could be improved, I'll make a bug report I guess although I'm not sure if this qualifies as a bug. Did you receive my email? Sent to an address with archlinux.org domain.
Sorry for the clutter in here @luzpaz but at least now you know @xyproto is the person to list as arch package maintainer.

@luzpaz
Copy link
Author

luzpaz commented Jun 16, 2022

Sorry for the clutter in here

No worries. I'm happy this is getting clarrified!

@luzpaz
Copy link
Author

luzpaz commented Sep 23, 2022

i've added an easy copy paste table at the top so maintainers can be pinged when necessary without the extra markdown or twitter info column

@xyproto
Copy link

xyproto commented Sep 23, 2022

@luzpaz Here's a fork/suggested edit of the Packagers.md gist: https://gist.github.com/xyproto/18dbf7000248bec8b2a89695daccfc7b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment