Bug 231351 - rename sysutils/docker-compose to sysutils/py-docker-compose
Summary: rename sysutils/docker-compose to sysutils/py-docker-compose
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Nikolai Lifanov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-13 20:56 UTC by Sven R
Modified: 2019-08-05 12:22 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (lifanov)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven R 2018-09-13 20:56:52 UTC
docker-compose should be renamed to py-docker-compose according to current naming convention.
(py27-docker-compose and py36-docker-compose)
Comment 1 Nikolai Lifanov freebsd_committer 2018-10-15 00:29:43 UTC
Hi! This port already generates a package for each version of Python.
In this case it's docker-compose and docker-compose-py36 by default.

Since it's an utility and not a library, suffix is acceptable and
might make it easier to discover.

Can you explain the motivation for this change please?
Comment 2 Sven R 2018-10-18 05:11:38 UTC
The motivation is to use a straightforward naming convention in ports. 
If a port requires Python as a basic programming language it should in the ports name not matter if it's a library or tool (e.g. py-certbot, py-iocage). That makes it much easier to keep stuff together using own mirrors and when using orchestration tools you can easily choose your corresponding Python version.
(I don't want to start a general discussion but as soon as py3 finally becomes standard Python version the packages must be renamed again "tool vs tool-py27". Using orchestration upgrading "tool" will then automatically install Python3.x.).
It's an enhancement request, not a bug. Just close this ticket if you disagree.
Comment 3 Walter Schwarzenfeld freebsd_triage 2019-08-05 12:22:05 UTC
Seems rejected, can we close here?