bug#40148: 26.3; Custom package header checked out from GIT in Windows will not parse

[Eli Zaretskii <eliz@gnu.org>]

> From: Noam Postavsky <npostavs@gmail.com>
> Cc: 40148@debbugs.gnu.org,  mangelozzi@gmail.com
> Date: Fri, 20 Mar 2020 15:47:27 -0400
> 
> > You are saying that creating a package (or a new file in a package)
> > should leave the EOL format of the Lisp files at "dos", and distribute
> > the package's files like that via the elpa's?
> 
> My message above says only what does happen, not what should happen (for
> the latter, see below).
> 
> But I'm not sure exactly what you mean by "create a package".

What I mean is that when someone makes a package, or more generally,
creates a Lisp file that will be made available for others on the
Internet, he/she should save that file with utf-8-unix.  IOW, the
Emacs default for saving new files is not what should determine the
EOL format of such files.  And that includes Lisp files that are part
of a package.

> About what should happen: I think detecting and giving a specific error
> about CRLF from package-buffer-info could be a satisfactory solution to
> this bug.  Or perhaps package-install-file could be more lenient.

Both solutions would be fine, IMO.