Andreas Enge <[email protected]> writes: >> Is there a way for me, as a channel maintainer, to have a single commit >> that works with Guix both before and after the package move? For >> example, I get a notification that package `foo' will be moved from >> `(gnu packages bar)' to `(gnu packages baz)'. What now? What changes >> do I make to ensure no issues for users of my channel? > > I think that if to every file with a > #:use-module (gnu packages bar) > you add a > #:use-module (gnu packages baz) > you should be good to go before and after the move (and may possibly > drop the first line after the move).
Oh, right, that should work. Though if `foo' will be the first package in `(gnu packages baz)', the module should be create when the deprecation process is started (even though it will be empty). And if `foo' is last package in `(gnu packages bar)', the module should be kept around for some time after the move (even though it will be empty), preferably with a warning on #:use-module. With these two edge-cases taken care of, this should be quite manageable for channels I would think. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
