Walk back confpkg caveats somewhat
It seems to be going well in practice.
This commit is contained in:
parent
fef289d069
commit
3eeb358212
14
config.org
14
config.org
|
@ -608,15 +608,13 @@ Now all that's needed is a template to be used.
|
||||||
;;
|
;;
|
||||||
;; Generated package (no.%n) from my config.
|
;; Generated package (no.%n) from my config.
|
||||||
;;
|
;;
|
||||||
;; This is liable to have unstated dependencies, and reply on other bits of
|
;; During generation, dependency on other aspects of my configuration and
|
||||||
;; state from other configuration blocks. Only use this if you know /exactly/
|
;; packages is inferred via (regexp-based) static analysis. While this seems
|
||||||
;; what you are doing.
|
;; to do a good job, this method is imperfect. This code likely depends on
|
||||||
|
;; utilities provided by Doom, and if you try to run it in isolation you may
|
||||||
|
;; discover the code makes more assumptions.
|
||||||
;;
|
;;
|
||||||
;; This may function nicely as a bit of self-contained functionality, or it
|
;; That said, I've found pretty good results so far.
|
||||||
;; might be a horrid mix of functionalities and state.
|
|
||||||
;;
|
|
||||||
;; Hopefully, in future static analysis will allow this to become more
|
|
||||||
;; properly package-like.
|
|
||||||
;;
|
;;
|
||||||
;;; Code:
|
;;; Code:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue