Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packaging #101

Closed
hugglesfox opened this issue Dec 17, 2019 · 9 comments
Closed

Packaging #101

hugglesfox opened this issue Dec 17, 2019 · 9 comments

Comments

@hugglesfox
Copy link

It would be great if Nebula provided deb and rpm packages to simplify the install and upgrade process.

@SaigyoujiYuyuko233
Copy link

agree! :) but the installation is simple. It just is a simple runnable file.

@coderobe
Copy link
Contributor

These should ideally be provided by downstream packagers of the relevant ecosystems to prevent incompatibilities and ensure distribution-local packaging standards - NixOS and Arch Linux are already doing that.
Consider bringing it up to the package maintainer(s) of the relevant distributions

@rawdigits
Copy link
Collaborator

I brought this in a comment on one of the arstechnica articles about nebula as well. We'd definitely prefer if other folks who enjoy using nebula might take up the task of packaging it for various distros/platforms, as @coderobe has done for Arch.

https://arstechnica.com/gadgets/2019/12/how-to-set-up-your-own-nebula-mesh-vpn-step-by-step/?comments=1&post=38425931

@toonsevrin
Copy link

toonsevrin commented Jul 7, 2020

I'll write a snapcraft package, hopefully this can then be CDed with the slack publisher.

EDIT: A snapcraft package has already been written: https://github.com/jwallden/nebula-snap

@hlovdal
Copy link

hlovdal commented Dec 13, 2021

I have created  rpm packages for my own usage that I have used on all my Fedora/Centos machines for a couple of months now. With those it is only install package, edit configuration file and then start and enable service.

(Now my package is "cheating" in the build process by just pulling the release binaries from this repository, which is why I have not made any pull requests yet.)

But related to this, I think just nebula is a very poor package name since

  1. It is not very descriptive.
  2. There exists other existing packages already named nebula.

I chose to name the package nebula-overlay-networking to avoid these issues.

Now that there exists a pull request for a Debian package I think it would be good to have a discussion on package name to avoid unnecessary naming fragmentation (like for example kdeconnect-kde, kdeconnect-plasma, kdeconnect or kde-connect).

Any maintainer opinions on package names?

@hlovdal
Copy link

hlovdal commented Dec 13, 2021

Related FreeBSD pull request.

@jdoss
Copy link
Contributor

jdoss commented Dec 13, 2021

  1. There exists other existing packages already named nebula.

This nebula software is no longer being maintained upstream and that package is being retired. I am working with the current maintainer of the nebula package in Fedora and EPEL to possibly take over the nebula in Fedora and EPEL name once EPEL 8 is no longer supported.

@jasikpark
Copy link
Collaborator

Created #630 since someone added nebula to homebrew complete w/ a service setup

@johnmaguire
Copy link
Collaborator

Hi there - we'd love to see packages for various distros but this is ultimately something to take up with the distro maintainers themselves.

I know Arch Linux, https://formulae.brew.sh/formula/nebula and Debian have packages, and there appears to be a snap package as well.

@johnmaguire johnmaguire closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants