unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Roel Janssen <roel@gnu.org>
Cc: 55538@debbugs.gnu.org
Subject: [bug#55538] [PATCH] gnu: virtuoso-ose: Update to 7.2.7.
Date: Wed, 25 May 2022 10:29:18 -0400	[thread overview]
Message-ID: <875ylt4rep.fsf@gmail.com> (raw)
In-Reply-To: <cfd0695b112fa6c8dda5a24d98ed826da3942079.camel@gnu.org> (Roel Janssen's message of "Fri, 20 May 2022 10:41:46 +0200")

Hi Roel,

Roel Janssen <roel@gnu.org> writes:

> Dear Guix,
>
> I'd like to update Virtuoso OSE to the latest release (see attached patch).
>
> Other than the version number and checksum bump I noticed that some JAR files made it in the build
> output.  I tried removing them from the source tarball using a snippet, but then one needs to
> include a patch for various Makefile.am files and run the autogen.sh script.  I thought this was
> simpler and clearer on what's actually achieved.

I fear in the future it would be easy to overlook the introduction of
extra bundled jars in the source, that'd get installed.  I feel it'd be
preferable if we removed them all from a source snippet, at the cost of
having to patch the build system (the extra complications you
mentioned).

Could you try it and send a revised patch?

Thanks!

Maxim




  reply	other threads:[~2022-05-25 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  8:41 [bug#55538] [PATCH] gnu: virtuoso-ose: Update to 7.2.7 Roel Janssen
2022-05-25 14:29 ` Maxim Cournoyer [this message]
2022-05-25 15:51   ` Roel Janssen
2022-05-27 10:47     ` Roel Janssen
2022-05-29 12:44       ` Efraim Flashner
2022-05-29 21:55         ` Roel Janssen
2022-05-30  6:21           ` Efraim Flashner
2022-05-30  7:09             ` bug#55538: " Roel Janssen
2022-05-31 13:44       ` [bug#55538] " Maxim Cournoyer

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=875ylt4rep.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=55538@debbugs.gnu.org \
    --cc=roel@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).