public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/perl-SQL-Translator] epel10: Split GraphViz-dependent components into subpackages
Date: Fri, 07 Aug 2026 12:46:37 GMT	[thread overview]
Message-ID: <178610679709.1.16350706577398412373.rpms-perl-SQL-Translator-0e5941e2cef4@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/perl-SQL-Translator
            Branch : epel10
            Commit : 0e5941e2cef4a1bbc8a9d6d11174428ef79f11f5
            Author : Adam Williamson <awilliam@redhat.com>
            Date   : 2022-02-07T13:52:18-08:00
            Stats  : +25/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/perl-SQL-Translator/c/0e5941e2cef4a1bbc8a9d6d11174428ef79f11f5?branch=epel10

            Log:
            Split GraphViz-dependent components into subpackages

Only a few parts of perl-SQL-Translator use GraphViz, but because
they're in the core package, the entire thing depends on graphviz
and its huge dependency chain (which includes GTK+2). Splitting
them out allows things that use SQL-Translator but not the
GraphViz features to avoid this dependency chain.

---
diff --git a/perl-SQL-Translator.spec b/perl-SQL-Translator.spec
index 48956cb..dd8c2cd 100644
--- a/perl-SQL-Translator.spec
+++ b/perl-SQL-Translator.spec
@@ -131,6 +131,21 @@ Summary:        ER diagram producer for SQL::Translator
 %description Producer-Diagram
 ER diagram producer for SQL::Translator.
 
+%package Producer-GraphViz
+Summary:        GraphViz diagram producer for SQL::Translator
+
+%description Producer-GraphViz
+GraphViz diagram producer for SQL::Translator.
+
+%package -n sqlt-graph
+Summary:        sqlt-graph tool to create a graph from a database schema
+Obsoletes:      %{name} < 1.62-4
+
+%description -n sqlt-graph
+The sqlt-graph tool from %{name} that can automatically create a graph
+from a database schema. Packaged separately to avoid the main package
+depending on Graphviz.
+
 %prep
 %setup -q -n SQL-Translator-%{version}
 # Fix shell-bangs
@@ -160,12 +175,22 @@ make test
 %{perl_vendorlib}/*
 %{_mandir}/man[13]/*
 %exclude %{perl_vendorlib}/SQL/Translator/Producer/Diagram.pm
+%exclude %{perl_vendorlib}/SQL/Translator/Producer/GraphViz.pm
 %exclude %{_mandir}/man3/SQL::Translator::Producer::Diagram.*
+%exclude %{_mandir}/man3/SQL::Translator::Producer::GraphViz.*
+%exclude %{_bindir}/sqlt-graph
 
 %files Producer-Diagram
 %{perl_vendorlib}/SQL/Translator/Producer/Diagram.pm
 %{_mandir}/man3/SQL::Translator::Producer::Diagram.*
 
+%files Producer-GraphViz
+%{perl_vendorlib}/SQL/Translator/Producer/GraphViz.pm
+%{_mandir}/man3/SQL::Translator::Producer::GraphViz.*
+
+%files -n sqlt-graph
+%{_bindir}/sqlt-graph
+
 %changelog
 * Fri Jan 21 2022 Fedora Release Engineering <releng@fedoraproject.org> - 1.62-5
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild

                 reply	other threads:[~2026-08-07 12:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178610679709.1.16350706577398412373.rpms-perl-SQL-Translator-0e5941e2cef4@fedoraproject.org \
    --to=awilliam@redhat.com \
    --cc=git-commits@fedoraproject.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