A nice feature (as a simpler alternative to layman-add) would be to add out-of-the-list overlays through the command line; e.g.: layman -t git -A git://example.com/myoverlay.git/ Just the simplest case, no useless details.
Honestly, I will not add this myself anytime soon. Patches welcome. Also, please contact <overlays@g.o.> if you need anything added to the list of public overlays. We're open to additions.
(In reply to comment #1) > Honestly, I will not add this myself anytime soon. Patches welcome. Do you have any wishes regarding the synopsis or output code? > Also, please contact <overlays@g.o.> if you need anything added to the list of > public overlays. We're open to additions. No, I don't need anything at the moment. But I guess some users may want to add their private overlays like so.
For a personal overlay I put custom xml list to layman.cfg. (http://github.com/divanorama/divan-overlay/raw/doc/divan-overlay.xml) I suggest that layman could also generate such xml like layman-make-xml -t git git://example.com/myoverlay.git/ And one more feature is to add such list to xml within a commandline layman --add-list http://github.com/divanorama/divan-overlay/raw/doc/divan-overlay.xml
(In reply to comment #2) > (In reply to comment #1) > > Honestly, I will not add this myself anytime soon. Patches welcome. > > Do you have any wishes regarding the synopsis or output code? If it extends the layman command, it needs to blend in with the current interface somehow. No concrete restrictions as of now. > No, I don't need anything at the moment. But I guess some users may want to add > their private overlays like so. I'm unsure if that's actually a good thing to make easy as it may keep overlays in the dark that otherwise may get requested for public addition. I'm not trying to argue the feature request away - just thinking loudly. (In reply to comment #3) > And one more feature is to add such list to xml within a commandline > layman --add-list > http://github.com/divanorama/divan-overlay/raw/doc/divan-overlay.xml layman's current option "-o" does that in a way. I'm not saying it's a full substitute, though.
(In reply to comment #3) > For a personal overlay I put custom xml list to layman.cfg. > (http://github.com/divanorama/divan-overlay/raw/doc/divan-overlay.xml) > > I suggest that layman could also generate such xml like > layman-make-xml -t git git://example.com/myoverlay.git/ > > And one more feature is to add such list to xml within a commandline > layman --add-list > http://github.com/divanorama/divan-overlay/raw/doc/divan-overlay.xml The layman-2 api now has the ability to accept an overlay definition defined in a python dictionary. It can then write out the xml to a file. This ability could be used in some code (internal in layman or an external tool) to create the xml file. Also, while not the same, it is still somewhat simpler... I have added the ability for layman to scan /etc/layman/overlays for any overlay definition xml files and add them to the layman.cfg overlays variable on initialization. This makes them pluggable, no editing required. Simply download a definition file to there and perform a fetch (for it to be in the cache) for it to be available. I do not intend to add this bugs feature enhancement to layman-2.0.0. I want to get a final release out soon. Perhaps it could be in 2.0.1 or 2.1 after the new api is settled in.
Layman now includes a tool called "layman-overlay-maker" which will assist the user in creating a proper overlay definition.
