From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Guix <guix-devel@gnu.org>
Subject: Make geckodriver part of Icecat package [Was: Packaging "single file"]
Date: Wed, 6 Nov 2019 09:12:53 +0100 [thread overview]
Message-ID: <20191106081253.cg4if6k7i5dlg7v2@rafflesia> (raw)
In-Reply-To: <20191105130421.vpycyhng5uont7zu@rafflesia>
Hi Guix,
As Jack answered my first question, I've changed the topic and rephrased
my questions for clarity.
Le 11/05, Tanguy Le Carrour a écrit :
> Le 11/04, Jack Hill a écrit :
> > On Mon, 4 Nov 2019, Tanguy Le Carrour wrote:
> > > I intended to ask this question later, but now that ungoogled-chromium
> > > has been superseded by icecat, I find myself stuck!
> > […]
> > Where are you getting stuck?
>
> I'm stuck with my UI tests! :-(
>
> I was relying on `chromedriver` (packaged with ungoogled-chromium), but now
> that it's been deprecated… I'm stuck! ^_^'
>
> `geckodriver` is not packaged with icecat. This is why I wanted to a)
> download it or b) package it.
>
> The problem is that a) the version I download does not work (a problem
> specific to Guix System, I guess, that would be solved by packaging…
> another wild guess) and b) it's a bit of work to package.
>
> But, all of sudden, I wonder if `geckodriver` could not be part of
> icecat, like `chromedriver` was part of ungoogled-chromium?!
1) could geckodriver be built and distributed with icecat? or
2) should I work on packaging it? or
3) is there a way to package the pre-built binary?
Regards,
--
Tanguy
next prev parent reply other threads:[~2019-11-06 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 15:04 Packaging "single file" Tanguy Le Carrour
2019-11-04 22:37 ` Jack Hill
2019-11-05 13:04 ` Tanguy Le Carrour
2019-11-05 15:31 ` Jack Hill
2019-11-06 8:12 ` Tanguy Le Carrour [this message]
2019-11-13 8:16 ` Make geckodriver part of Icecat package [Was: Packaging "single file"] Tanguy Le Carrour
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=20191106081253.cg4if6k7i5dlg7v2@rafflesia \
--to=tanguy@bioneland.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.