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

Create .deb package #28

Open
vitorbaptista opened this issue Oct 22, 2015 · 17 comments
Open

Create .deb package #28

vitorbaptista opened this issue Oct 22, 2015 · 17 comments
Labels

Comments

@vitorbaptista
Copy link
Owner

@vitorbaptista vitorbaptista commented Oct 22, 2015

It seems that we could open a RFP (Request For Package) with Debian at https://www.debian.org/devel/wnpp/. Check https://www.debian.org/doc/manuals/maint-guide/ as well.

@cuducos
Copy link

@cuducos cuducos commented Oct 22, 2015

Maybe a simpler way (even if palliative) would be to write a setup.py and use pip instead. I don't think it should be difficult to use entry_points={'console_scripts': … to add a command to users' path. Then the install & use instructions would be as simple as:

$ pip install shellshare
  …
$ shellshare
  Sharing session in http://shellshare.net/r/…

I might have time to give it a try in the weekend… but cannot promise.

@muggahtee
Copy link

@muggahtee muggahtee commented Oct 22, 2015

I think using pip would be a lot easier to manage than packages for every distro

@vitorbaptista
Copy link
Owner Author

@vitorbaptista vitorbaptista commented Oct 22, 2015

Although I enjoy pip and think it would be trivial to add it, I think building regular packages aren't much harder. This project is trivial, just needing to set a single file as executable, and depend on Python 2.7 and script (on the util-linux package in Ubuntu).

We basically need two packages: one for Debian and other for Homebrew. The .deb packages can be converted quite easily in any other, and the homebrew recipes seems easy to write. The hard part is to get into the default repositories.

@vitorbaptista
Copy link
Owner Author

@vitorbaptista vitorbaptista commented Mar 9, 2017

Thanks to @arthar360, we now have a package for Homebrew (#31). We only need to generate a .deb now, which can be converted to other distribution's package managers.

@vitorbaptista vitorbaptista changed the title Create packages for the main distributions + mac Create .deb package Mar 9, 2017
@phls
Copy link

@phls phls commented Dec 5, 2018

Hi. I was looking to package shellshare, but it depends too much nodejs modules not packaged in Debian yet.

I had to gave up for now.

@arthar360
Copy link

@arthar360 arthar360 commented Dec 6, 2018

@phls executing the public/bin/shellshare file should do the magic.

@phls
Copy link

@phls phls commented Dec 6, 2018

@arthar360 is public/bin/shellshare is the client?

@arthar360
Copy link

@arthar360 arthar360 commented Dec 6, 2018

image

Yes, Thats the client @phls . Does the file fail to execute?

@phls
Copy link

@phls phls commented Dec 6, 2018

@arthar360 no, its ok to me.

@vitorbaptista
Copy link
Owner Author

@vitorbaptista vitorbaptista commented Dec 7, 2018

Hey @phls, it's been a long time. Nice to see you here!

So, the shellshare client doesn't depend on NodeJS at all. Sorry, I think the install instructions are kinda confusing, as it's the server's install instructions.

As @arthar360 was saying, the package just need to add https://github.com/vitorbaptista/shellshare/blob/master/public/bin/shellshare to the executable path, which only depends on Python.

@phls
Copy link

@phls phls commented Dec 10, 2018

@vitorbaptista hi!

In this case, to have a package with just shellshare, it's better if you create another repository like "shellshare-client" with README, LICENSE, public/bin/shellshare and all files you need to the client.

@vitorbaptista
Copy link
Owner Author

@vitorbaptista vitorbaptista commented Dec 10, 2018

@phls
Copy link

@phls phls commented Dec 11, 2018

Answering in portuguse.

Me parece que o melhor para evitar complicações para todos é simplesmente não empacotar então.

Do jeito que está, para empacotar apenas o public/bin/shellshare será necessário excluir todo o resto que não é usado durante o processo de empacotamento, e criar um pacote como +DFSG. E eu pessoalmente não estou afim de puxar essa complicação para mim :-)

Como você não quer criar a complicação de seperar o software em outro repositório, melhor abandonar a ideia mesmo.

Abraços,

@vitorbaptista
Copy link
Owner Author

@vitorbaptista vitorbaptista commented Dec 12, 2018

@phls
Copy link

@phls phls commented Dec 12, 2018

humm, não faz muito sentido empacotar algo que não será usado.

O pacote não vai construir porque tem dependências não satisfeitas, incluindo aquele diretório onde estão os módulos nodejs.

@vitorbaptista
Copy link
Owner Author

@vitorbaptista vitorbaptista commented Dec 12, 2018

@phls
Copy link

@phls phls commented Dec 12, 2018

Não é isso. Se o pacote não constroi, ele não entra no Debian. É como se ele tivesse uma falha e por isso fica impossibilidade de entrar no repositório.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.