I think the rules for module branches should be stricter. After several
back and forth in discussions with Jun about stream branches for Ruby, I
believe that the concept of "using upstream major versions as branches"
[1] is not enough and can work just for the simplest cases.
We should use ${module}-${stream} branches everywhere (the "stream-"
prefix would be useful as well, because it would explain the semantics
use after the prefix).
For example, if we have "foo" module with "1.0" and "2.0"
streams and it
ships "bar" and "baz" components, the components should have
appropriate
"(stream-)foo-1.0" and "(stream-)foo-2.0" branches.
We could also utilize `git symbolic-ref` to link the branches if needed ....
Vít
Dne 16. 04. 19 v 15:25 Jun Aruga napsal(a):
Hi,
I like to see "package branch name" of each modules to be aligned more.
Here is a list of the current module, the module stream name, the
package branch name, another package name. There are some patterns on
the list.
# module, the module stream name (module/foo's branch), the package
branch name (rpms/foo's branch), another package name (rpms/bar's
branch)
mongodb 3.6 3.6 None
nodejs 8 8 None
perl 5.24 fXX fXX
python3 3.6 None None
python36 3.6 None master
ruby 2.5 ruby-2.5 master
scala 2.10 javapackages javapackages
varnish 6 stream-6 stream-6
See more detail at
https://pagure.io/jaruga-modules-branches
I think "None" is same with "master" technically.
In case of modules/ruby, we ruby team decided "the package branch
name" as "ruby-X.Y" with a module name prefix against "X.Y"
documented
in the naming guideline.
Because a package of a module A (ex. modules/ruby) can be used also in
a module B (ex. modules/rubygem-rails, modules/vagrant and etc.
In this case, a package branch name needs to have "ruby-X.Y",
"rubygem-rails-X.Y", "vargrant-X.Y".
Do you like to see some alignments for the naming?
Hopefully after the discussion here in this thread, below page will be updated.
https://docs.fedoraproject.org/en-US/modularity/making-modules/naming-gui...
Regards,
Jun
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org