bug#61802: 29.0.60; Packages supporting "package.el" throw comp warnings when package.el not loaded

bug#61802: 29.0.60; Packages supporting "package.el" throw comp warnings when package.el not loaded

[Chris Brolly]

[-- Attachment #1: Type: text/html, Size: 25896 bytes --]

[-- Attachment #2: bcsemailsig_52b4a686-8025-40b5-8c88-171d00a4dec3.png --]
[-- Type: image/png, Size: 8934 bytes --]

[-- Attachment #3: emailsigtool_60be44bb-cb75-4a7f-9f7a-664d2f213eea.png --]
[-- Type: image/png, Size: 2131 bytes --]

bug#61802: 29.0.60; Packages supporting "package.el" throw comp warnings when package.el not loaded

[No Wayman]

I imagine any alternative package manager which does not rely on 
package.el will see these warnings when byte-compiling. (I see 
them with Elpaca).
I don't see the point in byte-compiling them, so it may be worth 
suggesting a file-local no-byte-compile variable be added to such 
files.

bug#61802: 29.0.60; Packages supporting "package.el" throw comp warnings when package.el not loaded

[Stefan Kangas]

tags 61802 notabug
close 61802
thanks

Chris Brolly <Chris.Brolly@building-controls.com> writes:

> When packages are built (using straight-use-package) with native-comp
> enabled, many result in the warning such as the one resulting from magit
> being compiled below:
>     Warning (comp): magit-section-pkg.el:1:2: Warning: the function
>             'define-package' is not known to be defined.
>     Warning (comp): git-commit-pkg.el:1:2: Warning: the function
>             'define-package' is not known to be defined.
>     Warning (comp): magit-section-pkg.el:1:2: Warning: the function
>             'define-package' is not known to be defined.
>     Warning (comp): magit-pkg.el:1:2: Warning: the function
>             'define-package' is not known to be defined.
> This will happen after the initial straight.el build process is
> completed.
> I've tried to cut this down, but i was unable to replicate it without
> straight.el. Just using use-package on its own with another package was
> unsuccessful.
>
> (unless (featurep 'straight)
>   ;;(setq straight-repository-branch "rr-fix-renamed-variable")
>   (defvar bootstrap-version)
>   (let ((bootstrap-file
>          (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory))
>         (bootstrap-version 6))
>     (unless (file-exists-p bootstrap-file)
>       (with-current-buffer
>           (url-retrieve-synchronously
>            "https://raw.githubusercontent.com/radian-software/straight.el/develop/install.el"
>            'silent 'inhibit-cookies)
>         (goto-char (point-max))
>         (eval-print-last-sexp)))
>     (load bootstrap-file nil 'nomessage))
>   (setq my-straight-pkgs
>         '((use-package :type git :host github :repo "jwiegley/use-package")
>           (magit :type git :host github :repo "magit/magit")))
>   (dolist (pkg my-straight-pkgs)
>     (straight-use-package pkg)))
>
> Once run, the warnings begin to pile up over the next few
> minutes. Nothing else untoward seems to happen, but I was recommended to
> report this so here I am.

This is a bug in straight.el, which seems to be compiling "foo-pkg.el"
files.  It should not do that.  I recommend reporting this bug to the
straight.el maintainers.  Meanwhile, I'm closing this bug.

Thanks.