all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Tomáš Čech" <sleep_walker@gnu.org>
To: guix-devel@gnu.org
Subject: make packagers life easier
Date: Sun, 15 Mar 2015 18:00:33 +0100	[thread overview]
Message-ID: <20150315170032.GA14849@venom> (raw)

Hello Guix,

I'd like to share some thoughts about packaging to find I'm doing it
wrong or show that there is room for improvements. I don't think that
the proposed improvements are hard to implement (from algorithmic POV)
and I'm aware that all the things can be solved on my side, but that
is not the point.

Stop after/before phase
=======================

What it can help with?

- download sources of package without constructing URL
- prepare sources for creating or applying patch
- when preparing configure parameters you can stop right after
  configuration phase

How to implement?
- inject always failing phase into phases list

Another level of this feature could be even continuing of the build.


Ommit developed package from generations
========================================

How it can help?

When I work on packages I have to take care of handling generations
even when I don't care. It complicates removing old package builds
using `guix gc -d' and it is unwanted burden.

How to implement?
I'm not exactly sure, but not creating new generation with the package
could be sufficient.



Improve output of the build
===========================

What I miss?

Mostly one particular and obvious thing - after successful build print
the path of newly created store in well visible, easy-to-mouse and
easy-to-parse way.

example:

New store created: /gnu/store/s0meb0r1ngandl000ngh4shlead1ngt0-package-1.0/

Right now I need to dig that from any build message above.



And in future it would be nice to add some colors to output. It helps
with orientation speed a lot.

Thanks for reading,

S_W

             reply	other threads:[~2015-03-15 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 17:00 Tomáš Čech [this message]
2015-03-16 17:01 ` make packagers life easier Ludovic Courtès
2015-03-16 18:39   ` Andreas Enge
2015-03-17 12:01 ` Sree Harsha Totakura
2015-03-17 16:12   ` Ludovic Courtès

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=20150315170032.GA14849@venom \
    --to=sleep_walker@gnu.org \
    --cc=guix-devel@gnu.org \
    /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.