Create .deb package

[vitorbaptista]

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]

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.

[heyitsols]

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

[vitorbaptista]

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]

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.

[phls]

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]

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

[phls]

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

[arthar360]

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

[phls]

@arthar360 no, its ok to me.

[vitorbaptista]

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]

@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]

Why? It isn't possible to use it as is? I'd like to avoid any unnecessary complications, the client and server are pretty much tied together, changing one usually imply changing the other, and the server needs to serve the client (so I would need submodules or similar if they were in a separate repository). Too much work just for a single file.

[phls]

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]

Tem algum problema em incluir tudo no pacote, mesmo que só vá usar o `public/bin/shellshare`? Sabe se isso vai contra alguma política do Debian, ou se eles deixariam de incluir o .deb se ele fosse criado assim? O repositório é minúsculo, então acho que a diferença de tamanho do pacote vai ser negligível.

[phls]

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]

Mas você consegue ver algum problema com isso, além de aumentar denecessariamente o tamanho do pacote? Estou tentando entender se há uma maneira mais simples, mantendo a estrutura do repositório atual.

[phls]

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.