From: David Pirotte <david@altosw.be>
To: Catonano <catonano@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: g-golf
Date: Sun, 14 Jan 2018 11:10:28 -0200 [thread overview]
Message-ID: <20180114111028.798bfa11@capac> (raw)
In-Reply-To: <CAJ98PDzqrvZpOkfZyQX311mjP4dx7jO+7qEp4ofiv2mo=hgeQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
Hi Catonano,
> > Thank you for your interest, but please note that G-Golf still is in
> > planning stage
> I know but I tought I would have taken a look
Ok, you're welcome of course!
> I don't know if I will ever be able to contribute
> But the fiirst thing is that G-golf should have a guix.scm file and be
> buildable with Guix. I see that as my step 0
> Then, we'll see
I don't think so: to contribute, you should rather git clone, read as much as you
can (you need to grow a good knowledge of glib and gobject too...), ask questions,
then start to patch ... and send them to guile-devel, preceding messages with
'G-Golf', as stated on G-Golf main page...
No need to have any particular distro, just the autool chain and gnome
dependencies, as listed in the configure.ac ... (guix has all these of
course, but you could contribute/develop using any distro...
> > FI, the upstream configure step works perfectly well.
> What do you mean with "upstream" ?
Distro developers generally refer to 'upstream' as the development that is done
outside any particular distro. In this case, upstream is the g-golf git repo
at savannah (there is no tarball yet, since there has been no release) and it
requires 'the autotool chain' as its building system.
> I checked it out with git from the only repository that I know of
Ok: so just run the autotool danse, not a guix command
cd <g-golf-git-clone-dir>
./autogen.sh
./configure [--prefix=/your/prefix]
make
make check
[ no need to install, it is 'unusable' at this stage
> On which GNU/Linux distribution are you building it ?
> Which version of pkg-config are you using ?
Debian buster (testing), pkg-config 0.29-4+b1
> Can you make an ipothesis why pkg-config in my guix environment can't be
> found ?
Sorry, I don't
> Maybe I should move this discussion on the Guix mailing list ?
Be aware that I'm a member of guix-devel, but not guix-user. Then if the objective
is to contribute to G-Golf, I prefer we use guile-devel
Thanks again for your interest, it's nice someone pings me about this project, it
reminds me I really have to find some time to work o it...
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-01-14 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 10:03 g-golf Catonano
2018-01-14 10:08 ` g-golf Amirouche Boubekki
2018-01-14 10:46 ` g-golf Catonano
2018-01-14 12:00 ` g-golf David Pirotte
2018-01-14 12:17 ` g-golf Catonano
2018-01-14 12:35 ` g-golf Catonano
2018-01-14 13:09 ` g-golf Catonano
2018-01-14 13:10 ` David Pirotte [this message]
2018-01-14 13:32 ` g-golf Catonano
2019-06-19 22:35 ` g-golf status Mike Gran
2019-06-21 4:05 ` David Pirotte
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180114111028.798bfa11@capac \
--to=david@altosw.be \
--cc=catonano@gmail.com \
--cc=guile-user@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.
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).