unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vijayalakshmi Vedantham <vijimay12@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Internship on Improve the user experience for the "guix package" command line tool (Outreachy)
Date: Tue, 20 Mar 2018 20:45:02 +0530	[thread overview]
Message-ID: <CAD8c3_duj40tbxUkjvuKZvrEN126dV_g=RPMMntSKHoT83zqnA@mail.gmail.com> (raw)
In-Reply-To: <87in9qdcws.fsf@elephly.net>

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

Hi,

I'm really sorry about the effort you had to put into this patch. I'll try
not to do it again.

I had to append “.zip” because Pypi didn’t have a “.tar.gz” file for the
> sources, so the uri
> field now is:
>
>    (pypi-uri "logwrap" version ".zip")
>

Did you do this because only .zip is available here (
https://pypi.python.org/pypi/logwrap#downloads)?


>
> I also noticed that the sources include files that were generated with
> Cython.  Instead of reusing those, we build them from source.  Luckily
> all we have to do in this case is to add “python-cython” to the
> native-inputs field.
>

Can I know how you knew this?


> Finally, the tests. At first the tests wouldn’t run.  So I looked up the
> error message online and found that I need to use “python-pytest-runner”
> in addition to “python-pytest”.  This allows the tests to run up to a
> point until it wants to do coverage tests.  For those I needed to add
> “python-pytest-cov”.
>
> I changed the description, because I think it wasn’t quite correct.
>

Again, I'm sorry.


     Have you been able to build Guix already and try building the package
using “./pre-inst-env guix build”?

No, I tried last night but I faced some issues, I'll try again tonight.

Thanks,
Vijayalakshmi

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

  reply	other threads:[~2018-03-20 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAD8c3_e9+N2AEcR+fYs_bzsyLM9i85Fv1rT3P7jaPMKV+ihWog@mail.gmail.com>
     [not found] ` <CAD8c3_dj0sUOtb=kU4tCtLH1LesOQmkdSqDO+awvUFB8Q+8Q2A@mail.gmail.com>
     [not found]   ` <87fu5pch36.fsf@elephly.net>
     [not found]     ` <CAD8c3_c8hwg2pLdKvaPKyPzy+bgLVGekyF2vGVWFW-Fb-BX1ww@mail.gmail.com>
     [not found]       ` <87h8pfy56s.fsf@elephly.net>
     [not found]         ` <CAD8c3_foX-c-+j3jfkLHG1VcnL2u7s_ixj550XcU1Ch-Fbqtjg@mail.gmail.com>
     [not found]           ` <87tvtdthda.fsf@elephly.net>
     [not found]             ` <CAD8c3_fD241AogQiaQTo2g-vXcwrWjt9FhAejMh57ZB+cBmKKQ@mail.gmail.com>
     [not found]               ` <87k1u8uccr.fsf@elephly.net>
2018-03-19 16:58                 ` Internship on Improve the user experience for the "guix package" command line tool (Outreachy) Vijayalakshmi Vedantham
2018-03-19 20:27                   ` Ricardo Wurmus
2018-03-20 14:44                   ` Ricardo Wurmus
2018-03-20 15:15                     ` Vijayalakshmi Vedantham [this message]
2018-03-20 15:54                       ` Ricardo Wurmus
2018-03-20 18:34                       ` Björn Höfling
2018-03-21  8:35                       ` Efraim Flashner
2018-03-21 17:03                         ` Vijayalakshmi Vedantham
2018-03-21 19:44                           ` Gábor Boskovits

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to='CAD8c3_duj40tbxUkjvuKZvrEN126dV_g=RPMMntSKHoT83zqnA@mail.gmail.com' \
    --to=vijimay12@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).