How to Write Empty File in Build Phase?

How to Write Empty File in Build Phase?

[Antwane Mason]

[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]

Hello,

I am currently working to resolve a build issue of python-verspec with the
ultimate goal of submitting a package for this package, onlykey-cli, and
all other dependencies required for onlykey-cli. Onlykey is a hardware
password manager, second factor authenticator, and private key storage
manager. A working solution to the build problem is to include an empty
__init__.py file in the test folder of the source code. How do I write this
file during a build phase?

Here is the package definition for reference.
-----------------------------------
(define-public python-verspec
  (package
    (name "python-verspec")
    (version "0.1.0")
    (source
      (origin
        (method url-fetch)
        (uri (pypi-uri "verspec" version))
        (sha256
          (base32
            "07n06wv85fm4vl1ird2mja0823js3x322wgs9gdnq1djjyk4ql64"))))
    (build-system python-build-system)
    (native-inputs
      `(("python-coverage" ,python-coverage)
        ("python-flake8" ,python-flake8)
        ("python-mypy" ,python-mypy)
        ("python-pretend" ,python-pretend)
        ("python-pytest" ,python-pytest)))
    (home-page
      "https://github.com/jimporter/verspec")
    (synopsis "Flexible version handling")
    (description "Flexible version handling")
    (license '(license:asl2.0 license:bsd-2))))
-----------------------------------

Regards,
Antwane

[-- Attachment #2: Type: text/html, Size: 1972 bytes --]

Re: How to Write Empty File in Build Phase?

[muradm]

May be something like this? (e-mail adhoc typing, may require 
fixing)

(define-public python-verspec
  (package
    (name "python-verspec")
    (version "0.1.0")
    (source
     (origin
       (method url-fetch)
       (uri (pypi-uri "verspec" version))
       (sha256
        (base32
         "07n06wv85fm4vl1ird2mja0823js3x322wgs9gdnq1djjyk4ql64"))
       (modules '((guix build utils)))
       (snippet
        '(with-directory-excursion "test"
           (with-output-to-file "__init__.py"
             (newline))))))
    (build-system python-build-system)
    (native-inputs
     `(("python-coverage" ,python-coverage)
       ("python-flake8" ,python-flake8)
       ("python-mypy" ,python-mypy)
       ("python-pretend" ,python-pretend)
       ("python-pytest" ,python-pytest)))
    (home-page
     "https://github.com/jimporter/verspec")
    (synopsis "Flexible version handling")
    (description "Flexible version handling")
    (license '(license:asl2.0 license:bsd-2))))

You can use (snippet of (origin, that allows pre phases actions on 
source before
any build steps/phases. (with-directory-excursion will basically 
"cd" to "test"
directory, (with-output-to-file will open file named 
"__init__.py", (newline)
will write empty line to just opened file.

Antwane Mason <ad.mason1413@gmail.com> writes:

> Hello,
>
> I am currently working to resolve a build issue of 
> python-verspec with the ultimate goal of submitting a package 
> for this
> package, onlykey-cli, and all other dependencies required for 
> onlykey-cli. Onlykey is a hardware password manager, second
> factor authenticator, and private key storage manager. A working 
> solution to the build problem is to include an empty
> __init__.py file in the test folder of the source code. How do I 
> write this file during a build phase?
>
> Here is the package definition for reference.
> -----------------------------------
> (define-public python-verspec
>   (package
>     (name "python-verspec")
>     (version "0.1.0")
>     (source
>       (origin
>         (method url-fetch)
>         (uri (pypi-uri "verspec" version))
>         (sha256
>           (base32
>             "07n06wv85fm4vl1ird2mja0823js3x322wgs9gdnq1djjyk4ql64"))))
>     (build-system python-build-system)
>     (native-inputs
>       `(("python-coverage" ,python-coverage)
>         ("python-flake8" ,python-flake8)
>         ("python-mypy" ,python-mypy)
>         ("python-pretend" ,python-pretend)
>         ("python-pytest" ,python-pytest)))
>     (home-page
>       "https://github.com/jimporter/verspec")
>     (synopsis "Flexible version handling")
>     (description "Flexible version handling")
>     (license '(license:asl2.0 license:bsd-2))))
> -----------------------------------
>
> Regards,
> Antwane

Re: How to Write Empty File in Build Phase?

[Antwane Mason]

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

muradm,

Thank you so much for your help! That worked like a charm! Just needed to
adjust the second argument of with-output-to-file so that it takes a lambda
that returns (newline).
Here is the resulting package definition that successfully builds.

(define-public python-verspec
  (package
    (name "python-verspec")
    (version "0.1.0")
    (source
      (origin
        (method url-fetch)
        (uri (pypi-uri "verspec" version))
        (sha256
          (base32
            "07n06wv85fm4vl1ird2mja0823js3x322wgs9gdnq1djjyk4ql64"))
        (modules '((guix build utils)))
        (snippet
        '(with-directory-excursion "test"
           (with-output-to-file "__init__.py"
             (lambda () (newline)))))))
    (build-system python-build-system)
    (native-inputs
      `(("python-coverage" ,python-coverage)
        ("python-flake8" ,python-flake8)
        ("python-mypy" ,python-mypy)
        ("python-pretend" ,python-pretend)
        ("python-pytest" ,python-pytest)))
    (home-page
      "https://github.com/jimporter/verspec")
    (synopsis "Flexible version handling")
    (description "Flexible version handling")
    (license '(license:asl2.0 license:bsd-2))))

Regards,
Antwane

[-- Attachment #2: Type: text/html, Size: 1906 bytes --]

Re: How to Write Empty File in Build Phase?

[Tobias Geerinckx-Rice]

Hi Antwane,

> (with-output-to-file "__init__.py"
>  (lambda () (newline))

=>

   (with-output-to-file "__init__.py"
     newline)

Untested, but NEWLINE taking #:optional arguments should not make it any 
less of a thunk.

Kind regards,

T G-R

Sent from a Web browser.  Excuse or enjoy my brevity.

Re: How to Write Empty File in Build Phase?

[Antwane Mason]

[-- Attachment #1: Type: text/plain, Size: 216 bytes --]

 > (with-output-to-file "__init__.py"
 >    newline)

> Untested, but NEWLINE taking #:optional arguments should not make it any
> less of a thunk.

That code snippet worked well for me. I appreciate the suggestion!

[-- Attachment #2: Type: text/html, Size: 399 bytes --]