Closed thet closed 1 month ago
BTW, do you and @jensens indeed prefer to split the sources and checkouts in two files? I would be fine with either one or two files, but two files make it a bit easier to translate between our current buildout config and mxdev, so I would be happy with that approach. A short checkouts.ini
makes it easier to see which packages are checked out.
BTW, several commands already work on both buildout and mxdev files. If you temporarily rename or copy checkouts.ini
to mxdev.ini
, you get this:
$ bin/manage check-checkout Products.CMFPlone
YES, your package Products.CMFPlone is on auto checkout in mxdev.ini.
YES, your package Products.CMFPlone is on auto checkout in checkouts.cfg.
I think having 3 files has it advantages.
mx.ini
over all setupmxsources.ini
(yes prefix, so it stands together) mxcheckout.ini
with only the checkouts.This way one may use only sources with own checkouts/branches(think PLIPS) overrides.
Closing this in favour of https://github.com/plone/buildout.coredev/pull/945.
Add scripts to create mxdev compatible ini files from sources.cfg and checkouts.cfg.
This feature is useful with the mxdev
include
feature, available since mxdev 3.1.0 and done at the Kitchen Sprint 2023 in Völs. See: https://github.com/mxstack/mxdev/pull/37TODO