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
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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
Comment by Dave Reisner (falconindy) - Saturday, 27 July 2013, 14:27 GMT
> easier for new archlinux users to find packages.
$ 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.
Comment by niels abspoel (aboe) - Saturday, 27 July 2013, 15:19 GMT
> easier for new archlinux users to find packages.
> $ 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.
Comment by Gaetan Bisson (vesath) - Sunday, 28 July 2013, 02:06 GMT
Splitting openssh into client and server would make our PKGBUILD and dependencies more complex for very little gain. Since the current package is not big, it is really not a problem installing both client and server even if you only need the server. So I really see no reason to go against the Arch tradition on this one.

Loading...