fedora-modularity / f27-content-tracking Goto Github PK

help2man states the package is in autotools. It isn't. It's in a separate help2man:f27 module.

net-tools should only be in one or shared.

Please clarify what "dhcp" module means. If it is meant for dhclient, then these two modules should be merged. Both, client and server are build from a single SRPM, therefore I think we should provide "client" / "server" profiles of the DHCP module, instead of two modules...

hardware-support, host, maven, ninja, and platform modules are not in f27-content-tracking. Also only one of nodejs streams is mentioned there.

/cc @whitel @asamalik @KarstenHopp

vsftpd is preferred FTP server implementation, as it is the one supported also in Enterprise Linux

We need the process and guidelines approved to allow people to create modules in Fedora.

• Process
• Guidelines
• FESCo Approval ticket

they seem to be mostly failed builds of cassandra .. not what they claim to be

The f27 postgresql module currently defines only client and default install profiles; we should add server too.

Last time I requested systemtap module because ruby module depends on it.
But the ruby module could be built without the systemtap module, as I removed the systemtap build dependency in rpms/ruby by conditional macro.

So, we may be able to remove the systemtap module from targeted.
https://github.com/fedora-modularity/f27-content-tracking

Checking the Boltron images shows that Python 2 is currently installed by default, rather than only being installed as part of the Python 2 module (note that the "Installed" column is empty for the latter command):

$ docker run --rm -it jamesantill/boltron-27 rpm -qa python2
python2-2.7.13-18.module_72e25b65.x86_64

$ docker run --rm -it jamesantill/boltron-27 dnf module list python2
Fedora - Bikeshed - Developmental packages for the next Fedora release
Name                      Stream                            Version                         Profiles                            Installed                  Info                                                   
python2                   master (default)                  20171003150125                  default, full, ...                                             Python programming language, version 2

We need bodhi to understand modules so we can ship updates to them

• Fedora Change
• Tracker Bug #1352587

We need the arbitrary branching to make real changes to modules.

• Fedora Change
• Tracker bug: #1458665

f27 samba module currently has only the "default" profile; we should provide easy installation of either the client or server components.

f27 freeipa module currently has only the "default" profile; we should provide easy installation of either the client or server components.

A major point of modularity is to support content streams that have lifecycles independent of the base distribution.

So module streams should have names reflecting the lifecycle of the module content itself, not a generic stream name like the current "master".

Modules like "http", "samba", "bind" etc. should have a stream name reflecting the (major) version of the primary component.

Open question: should platform&host modules use stream name "27" or something else?

How hard would it be to fix up the f26 modules to work with the f27 base? Could we easily have two streams of a few things?