unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 48024@debbugs.gnu.org
Subject: bug#48024: glib-2.62.6 build fails i686
Date: Sat, 8 May 2021 15:26:43 +0200	[thread overview]
Message-ID: <20210508132643.GA12344@LionPure> (raw)
In-Reply-To: <87tunel9mt.fsf@netris.org>

Hi Mark,

tl;dr -- would you by chance have a mhw-bootstrap.sh that could clone
your set-up of a private git repo to use the way you often mention doing?

I am interested in doing it your way  ;)

IIRC, Pjotr wrote extensive notes on how to build starting with a git clone,
but ended up advising against doing it unless there was no other way.

Any tips appreciated :)
TIA.

On +2021-05-07 13:46:07 -0400, Mark H Weaver wrote:
> Hi,
> 
> Bone Baboon <bone.baboon@disroot.org> writes:
> > How can I use the glib I have built in a system configuration while this
> > fix or a variation of it makes it's way into the Guix master branch?
> 
> I guess that you'll need to set up a personal branch of Guix, like I do,
> with a patch applied to the 'glib' package, and another patch applied to
> 'inetutils' (referring to <https://bugs.gnu.org/48214#35>).
> 
> My recommendation, for now, would be to do this:
> 
> (1) Set up your own git repository, with a personal branch that's the
>     same as our official 'master' branch plus the additional patches
>     that you need, and to periodically rebase this branch on top of our
>     'master' branch.
> 
> (2) On all of your systems that need these customizations, pass the
>     "--url=URL" and "--branch=BRANCH" options to "guix pull", each time
>     you use that command.
> 
> There _might_ be a nicer way to set this up using channels, but I've
> never used channels and am mostly ignorant of them.  Maybe someone else
> can chime in on that point.
> 
>       Regards,
>         Mark
> 
> -- 
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts.  Ask me about <https://stallmansupport.org>.
> 
> 
> 

-- 
Regards,
Bengt Richter




  reply	other threads:[~2021-05-08 13:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26  3:35 bug#48024: glib-2.62.6 build fails i686 Bone Baboon via Bug reports for GNU Guix
2021-04-26 15:26 ` raingloom
2021-04-27 19:25   ` Bone Baboon via Bug reports for GNU Guix
2021-04-28  3:23     ` Mark H Weaver
2021-05-03 22:00       ` Bone Baboon via Bug reports for GNU Guix
2021-05-04  0:38         ` Leo Famulari
2021-05-04  3:01         ` Mark H Weaver
2021-05-04  6:18           ` Efraim Flashner
2021-05-04 20:01             ` Mark H Weaver
2021-05-04 20:08               ` Mark H Weaver
2021-05-04 22:52               ` Bone Baboon via Bug reports for GNU Guix
2021-05-05  8:38               ` Efraim Flashner
2021-05-05 21:15                 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06  0:20                   ` Mark H Weaver
2021-05-06  0:35                     ` Bone Baboon via Bug reports for GNU Guix
2021-05-06  6:45                   ` Efraim Flashner
2021-05-06  9:06                     ` Bengt Richter
2021-05-06 17:44                     ` Bone Baboon via Bug reports for GNU Guix
2021-05-07 17:46                       ` Mark H Weaver
2021-05-08 13:26                         ` Bengt Richter [this message]
2022-03-18  2:26                     ` Maxim Cournoyer
2021-05-04  3:56         ` Mark H Weaver
2021-05-05 16:34           ` Bone Baboon via Bug reports for GNU Guix
2021-05-06  8:46             ` Mark H Weaver
2021-05-06 19:36               ` Bone Baboon via Bug reports for GNU Guix

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=20210508132643.GA12344@LionPure \
    --to=bokr@bokr.com \
    --cc=48024@debbugs.gnu.org \
    --cc=mhw@netris.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).