From: ng0@n0.is
To: guix-devel@gnu.org
Subject: Re: Policy to remove obsolete packages
Date: Tue, 5 Feb 2019 21:31:53 +0000 [thread overview]
Message-ID: <20190205213134.yluu4butrdrcy6uj@uptimegirl.lan> (raw)
In-Reply-To: <20190205111301.2070ec2d@alma-ubu>
Bjrn Hfling transcribed 846 bytes:
> On Mon, 04 Feb 2019 23:52:47 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>
> > (Note that, IIUC, in openSuSE a package can be broken and yet remain
> > installable by users, because the last binary that was produced is
> > still around.)
>
> We have guix pull --commit=..., inferiors, channels and time-travel, so
> there are plenty opportunities to keep old states :-)
There are many ways to keep it, but they are really sometimes just jumping through too many hoops.
Or depending on what your idea of keeping old packages is. it should be easy, but
it involves a good amount[1] of work to build a much older version
with the otherwise almost-only recent,updating,master.
To the point where you have to do the logical thing and look into
which versions upstream or guix build around that time as dependencies
and simply "freeze" all the dependencies in your package.
1: amount depending on what you are building
There are other ways to handle obsolete packages, but I think they
don't map to how guix works:
a year or 2 back i experimented with a complete resructure of Guix,
and packages got split up differently (one module per package mostly)
leading to different kinds of problems and fixes.
a separate repository with the prefix -wip holds all the unstable,
obsolete, unfinished, etc packagesi (remotely comparable to how
ports trees are handled, but not quiet like it[1]). That's the gist
of it. just have a repository instead of dropping it from a tree.
Once it's fixed up in the "wip" repository, move it back into the
main repository.
I can elaborate more on this if you want me to once I'm no longer sick.
> Björn
>
next prev parent reply other threads:[~2019-02-05 21:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 11:16 Policy to remove obsolete packages Björn Höfling
2019-02-04 11:51 ` Pjotr Prins
2019-02-04 18:06 ` Andreas Enge
2019-02-04 22:18 ` Leo Famulari
2019-02-04 23:47 ` zimoun
2019-02-05 10:24 ` Björn Höfling
2019-02-07 12:40 ` zimoun
2019-02-08 8:47 ` Björn Höfling
2019-02-04 22:52 ` Ludovic Courtès
2019-02-05 10:13 ` Björn Höfling
2019-02-05 21:31 ` ng0 [this message]
2019-02-05 22:47 ` swedebugia
2019-02-05 23:52 ` ng0
2019-02-06 22:32 ` Ricardo Wurmus
2019-02-07 12:42 ` swedebugia
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=20190205213134.yluu4butrdrcy6uj@uptimegirl.lan \
--to=ng0@n0.is \
--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 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).