On Tue, 3 Feb 2015 18:01:21 +0300 Andrew Savchenko <[email protected]> wrote:
> On Tue, 3 Feb 2015 17:37:49 +0300 Andrew Savchenko wrote: > > 4. I don't fully understand how new plugin system is supposed to > interact with layman. > > I far as I can see, the global goal is to replace layman by new > sync system: it already supports git and svn, which covers most of > overlays. For more exotic ones there is a laymanator sync-type. > > If I'm right in my guess above, a question arises: how users should > maintain overlays via sync plugins then? Right now layman is very > convenient in adding and removing overlays: user needs only to > provide overlay name and have a nice list of overlays available. > With sync-plugins approach one have to enter all sync-uri paths > manually, which is annoying at least, irritating at last, since > many parameters have to be entered manually: location, sync-type, > sync-uri, auto-sync. Is there any tool to manage this stuff in a > friendly way? > > Best regards, > Andrew Savchenko NO, this new code does not, nor was it intended to __REPLACE__ layman. It is actually the opposite. The old sync code could handle rsync, git, cvs. It was a cludge mess of difficult to deal with code. There were also numerous requests to merge layman into portage. For portage to be able to handle all repo types,... This new plug-in system makes it easy to create and install new modules, or for other packages to install custom sync modules (AKA layman and it's laymanator module) which will let emerge, or more precisely, emaint sync layman overalys using layman through it's laymanator module. The new emaint sync module was modelled after layman's sync functioning. After all "I am also layman's lead developer", I was the one that had Devan <twitch153> create the laymanator module for portage as well as other improvements. This was all done as part of his GSOC 2014 project. Layman's commands are still used to install, remove overlays. The new sync does not remove layman's sync capability, just gives it an alternative interface, simplfying daily/weekly/monthly/... syncing. Recent layman versions are also fully capable of repos.conf style configs and does not require the old make.conf style configuration. It is capable of both types simultaneously, and of migrating from make.conf style to repos.conf style with only a few steps on the users part. See the wiki page [1] for more detailed migration instructions. https://wiki.gentoo.org/wiki/Project:Portage/Sync -- Brian Dolbec <dolsen>
signature.asc
Description: PGP signature
