Moduleset Specifications
Brought to you by:
dirkwallenstein
Menu
▾
▴
#2 Moduleset Specifications
There is this awful ambiguity concerning Moduleset Location Prefixes. The
prefix 'r:' is repository group relative if a path separator is contained in
the remainder, and moduleset repository relative if not. This affects the
'o:' prefix and makes it hard to arrange modulesets in subdirectories.
I'm thinking about the introduction of a new prefix 'm:' that explicitly picks
modulesets from the moduleset repository, and make 'r:' always only repository
group relative.
If there are a chunks of dependencies that vary in a few settings, it would be
possible to arrange dependencies in subdirectories without requiring absolute
specifications (or creating long skip configurations).
For example, the project's main moduleset could require the moduleset 'os-deps'
and the initial configuration for a Linux system could contain this section:
[core.moduleset-repo]
online-access = http://...
modulesets = o:project o:linux/os-deps
The advantage is that this would completely hide unneeded dependencies from
users.
It would also be interesting (unsure if actually useful or featureitis) if the
moduleset repository could be accessible as a module. This could facilitate
editing modulesets and posting patches. By default, I guess, the
moduleset-repo-module should be pulled manually, but there could also be
configuration to automatically update those modules before staging modulesets.
This is what the configuration could look like in the X.org use case, where the
modulesets are in the module 'modular':
[core.moduleset-repo]
modulesets = m:modular:xorg
auto-update-moduleset-modules = yes
Alternatively the prefix could be uppercase 'M:' to not put a restriction on
characters in modules or file names.
I guess, this should then be used exclusively. The clone-URL configuration
should best be removed to avoid duplication and diverging URLs.
This would then mean, that one would always have to start with an online
location, which should probably be the default, anyway.
<rich-text make="slant">
Ok, this does not look like made for a discussion, but you can comment without having an account here.
</rich-text>
There isn't rich text either (AFAICT) but for now I'll add my new comments in the ideatorrent:
https://sourceforge.net/apps/ideatorrent/x-jhbuild/ideatorrent/idea/1/