OVERVIEW
========
As the modularity work starts to enter Fedora with the Fedora 27
release, a typical Change Proposal did not seem to do justice on
capturing the moving parts and dependencies for the work to successfully
land. As a result, this document attempts to capture, at a high level,
the goals and deliverables for F27. We are also providing links to the
details to most aspects. Some of the details are still in progress and
will change over the F26 lifecycle (e.g. which modules will be included
for F27 Server).
THE GOAL
========
The Modularity and Server Working Groups plan, with the help of many
other groups in Fedora, to deliver a fully modularized version of the
Fedora Server Edition. As an equal and complementary goal, the tooling
for module creation/development, deployment and automatic testing will
be as simple and automated as possible.
[*Change*](https://fedoraproject.org/wiki/Changes/Modular_Server)
CAVEATS
=======
- Although modularity allows for lifecycle changes, there is no plan
for anything besides the normal 13 month lifecycle at this point.
- Available content as modules will be less than a typical Server release
- Only components that are a part of a module will be available
- Any RPM that is a part of module will be available to be
installed directly or in addition to the “install profile” install of
the module
ASPECTS TRACKED
===============
- Infrastructure Changes/Improvements:
- Bodhi: changes to support updating & tracking modules:
[*Change*](https://fedoraproject.org/wiki/Changes/ModularRelease)
- Arbitrary branching: enables modules to versions bound to
something other than Fedora release number:
[*Change*](https://fedoraproject.org/wiki/Changes/ArbitraryBranching)
- Bugzilla & ABRT module-awareness are still in progress
- COPR: support for building modules has been added and will be
improved over the F26 cycle
- Automation (Freshmaker)
- On Demand Compose Service (for testing and container rebuilds)
- Greenwave: for policy/gating in Bodhi. User interactions
take place in Bodhi.
- Installation & System Management
- Anaconda: still in progress
- DNF: Work underway to support modules, additional features need
to be added. Please report comments/features/bugs in the [*normal
manner*](https://github.com/rpm-software-management/dnf/wiki/Bug-Reporting).
- Gnome Software: still in progress
- Host & Platform module(s): Base components that provide the
“operating system” aspects of Modular Fedora:
[*Change*](https://fedoraproject.org/wiki/Changes/Host_and_Platform),
[*Content tracker*](https://github.com/fedora-modularity/hp)
- Application modules ([*Content
Tracking*](https://github.com/fedora-modularity/f27-content-tracking))
- TBD language modules (1 or more versions each)
- TBD database modules (1 or more versions each)
- TBD web server modules (1 or more versions each)
- TBD utility server modules (1 or more versions each)
- Applications as System Containers ([*Content
Tracking*](https://github.com/fedora-modularity/f27-content-tracking))
- TBD system integrated containers
- Module Guidelines and Processes:
[*Ticket*](https://pagure.io/Fedora-Council/tickets/issue/123)
- HowTos, Examples, and Tools for Modules:
[*Website*](https://docs.pagure.org/modularity/)
BENEFITS FOR USERS
==================
- Content available in multiple streams - good examples needed
- Software Collections done the right way - Languages, Databases
- No visible change to dnf/yum unless you want to select non-default
versions
FURTHER DETAILS
===============
- [*Bodhi
Milestone*](https://github.com/fedora-infra/bodhi/milestone/4) for
Modularity
- Bodhi Changes [*Focus
document*](https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/Bod…
- Freshmaker Focus doc
[*https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/Freshmaker*](https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/Freshmaker)
- ODCS Focus doc
[*https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ODCS*](https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ODCS)
- Branching Focus doc
[*https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching*](https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching)
Langdon White
Fedora Modularity Objective Lead
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
Hi,
as announced, yesterday I built nodejs-8.1.2 in rawhide.
Please, check that your packages work, especially native modules,
as there seem to be a few incompatibilities.
We also got new npm@5, which is said to be a little buggy.
Regards
Zuzka
I am trying to package the following from github for fedora. (Actually, I have been using my own RPM for years so it is hopefully not a major task).
https://github.com/maitra/thaali
Anyway, I wanted to ask how I should put the Source code from there
The source is at:
https://github.com/maitra/thaali/archive/master.zip
but that does not give me the version, etc number to build from the spec file.
So, what should I do?
Thanks again!
= Proposed Self Contained Change: Decouple system java setting from
java command setting =
https://fedoraproject.org/wiki/Changes/Decouple_system_java_setting_from_ja…
Change owner(s):
* Michael Simacek <msimacek AT redhat DOT com>
* Mikolaj Izdebski <mizdebsk AT redhat DOT com>
Alternatives can be used to specify which Java installation should be
the default for the system. Currently, changing the default java
command causes not only a change to the /usr/bin/java symlink, but
also affects the which runtime is used for system installed Java
applications. We propose introduction of separate setting for
system-wide java applications.
== Detailed Description ==
Fedora allows parallel installation of multiple Java runtime
environments and it uses alternatives mechanism to allow the user to
switch between them. JDK packages provide a set of alternatives
symlinks for it's executables. The java symlink is used to determine
the java command (/usr/bin/java), but also determines which runtime
environment is used to run system-wide Java applications installed
from RPMs, such as maven or eclipse. While in theory different Java
runtime environments are drop-in replacements for each other, in
practice some of the applications may stop working properly. Users
usually install alternative JDKs in order to run their own
applications and don't expect that changing the java command will have
effect on the system applications. By introducing a separate setting
for system-wide java, we would avoid this problem. We propose
specifying default Java runtime for RPM-managed applications in
/etc/java/java.conf (this is already possible, but not currently
used). Administrators would still be able to override the system
default if they need to.
== Scope ==
* Proposal owners:
Adjust javapackages-tools to provide default Java setting in /etc/java/java.conf
* Other developers:
N/A (not a System Wide Change)
* Release engineering:
https://pagure.io/releng/issue/6831
* List of deliverables:
N/A (not a System Wide Change)
* Policies and guidelines:
N/A (not a System Wide Change)
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
perl-Prima-1.52-1.fc27 changed license from
BSD and MIT and TCL and ImageMagick and LGPLv2+
to
BSD and MIT and TCL and ImageMagick and LGPLv2+ and AGPLv3+.
-- Petr