all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: mikadoZero <mikadozero@yandex.com>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: guix lint questions
Date: Thu, 21 Mar 2019 03:37:28 +0100	[thread overview]
Message-ID: <87y359c5qv.fsf@nckx> (raw)
In-Reply-To: <cuclg19j7y1.fsf@yandex.com>

mikadoZero,

mikadoZero wrote:
> I have three questions about the output of:
> `./pre-inst-env guix lint emacs-ace-link`
>
> 1)  What is the significance of:
>
> ;;; note: source file 
> /home/guix/u/guix/guix/gnu/packages/image-processing.scm
> ;;;       newer than compiled 
> /home/guix/u/guix/guix/gnu/packages/image-processing.g
> o                                                                                  
> ;;; note: source file 
> /home/guix/u/guix/guix/gnu/packages/image-processing.scm
> ;;;       newer than compiled 
> /run/current-system/profile/lib/guile/2.2/site-ccache/
> gnu/packages/image-processing.go                                                   
>
> This shows up many times for different scm files.

There is none.  These are mere warnings that the pre-built object 
files no longer match the source files you have checked out 
(i.e. the sources have changed).  They have nothing to do with 
your package.

You can use ‘guix environment guix -- make’ to make them go away 
if they really annoy you.

I just ignore them.

> 2)  How should this be addressed?
>
> gnu/packages/emacs-xyz.scm:1099:5: emacs-ace-link@0.5.0: the 
> source URI should not b
> e an autogenerated tarball
>
> Line 1099 is referring to origin.

You're downloading a ‘github.com/…/achive/…’ tarball.  These 
tarballs aren't guaranteed to be stable over time (GitHub can 
regenerate them, changing the metadata and hence the hash, and has 
done so in the past).

They must not be used.

Instead, use (method git-fetch), (git-reference …) and friends to 
download the git repository directly.  Tonnes of examples of this 
in Guix already, unfortunately, since many projects can't be 
bothered to make proper releases…  GitHub culture?

See ‘progress’ in gnu/packages/admin.scm for an example.  Don't 
forget to add (file-name (git-file-name name version)) when doing 
this, by the way.

> 3)  How should this be addressed?
>
> /home/guix/u/guix/guix/gnu/packages/emacs-xyz.scm:1095:2: 
> emacs-ace-link@0.5.0: line
>  1113 is way too long (417 characters)
>
> Line 1113 is referring to the text of the description.
>
> Looking at other packages in emacs-xyz.scm there are other 
> packages that
> have longer descriptions than the one here for emacs-ace-link.

Yes, but they're not all on one single line.  ;-)

Add a few well-placed newlines to wrap the text to eighty 
characters and the warning will go away.

Kind regards,

T G-R

  reply	other threads:[~2019-03-21  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  2:08 guix lint questions mikadoZero
2019-03-21  2:37 ` Tobias Geerinckx-Rice [this message]
2019-03-22 16:37   ` mikadoZero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y359c5qv.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=mikadozero@yandex.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.