FS#36295 - openssh package split client/server
Attached to Project:
Arch Linux
Opened by niels abspoel (aboe) - Saturday, 27 July 2013, 09:13 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 28 July 2013, 02:06 GMT
Opened by niels abspoel (aboe) - Saturday, 27 July 2013, 09:13 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 28 July 2013, 02:06 GMT
|
Details
Description:
Archlinux openssh package is a monolithic installation, The package provides both client and server. I propose to split the package in - openssh-server - openssh-client This has several advantages: The package comes in line with other distribution namingschemes. Which will make it easier for new archlinux users to find packages. Automation software modules for puppet/chef/salt can be reused which will make adoption/creation for archlinux much easier. Lean installations is possible, if you only want the client part, just install openssh-client. Steps to reproduce: # pacman -S openssh You get both openssh-client and openssh-server. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Sunday, 28 July 2013, 02:06 GMT
Reason for closing: Won't implement
Sunday, 28 July 2013, 02:06 GMT
Reason for closing: Won't implement
$ pacman -Ss openssh # seems to work pretty well for finding the package.
> The package comes in line with other distribution namingschemes.
Arch has a long history of naming things the way upstream names them. We aren't other distributions, and we don't try to be.
> make adoption/creation for archlinux much easier
This has never been an explicit goal of the project.
> $ pacman -Ss openssh # seems to work pretty well for finding the package.
That I know, but using a puppet module or chef module that is created for other distributions, You need to change the
whole module, because, you can't redeclare the same package for different things.
> The package comes in line with other distribution namingschemes.
> Arch has a long history of naming things the way upstream names them. We aren't other distributions, and we don't try to be.
I can understand this, but openssh-client and openssh-server won't be that different, it is still openssh.
The same thing has been done to mariadb and mariadb-client, obex-client and obex-server, x2go-agent and x2go-server
So it seems there are exceptions...
> make adoption/creation for archlinux much easier
> This has never been an explicit goal of the project.
Ok the weakest reason I gave, and you are right.