On Tue, Dec 29, 2020 at 10:48:53PM +, FreedomBen via devel wrote:
> Re: Matthew, at this point I only need one spec file version per
> Fedora/CentOS/RHEL version (mostly depends on which version of gcc is
> installed in the target distro), IOW it's totally fine for only one
> version to be avai
Thanks Andy, that's helpful.
Re: Matthew, at this point I only need one spec file version per
Fedora/CentOS/RHEL version (mostly depends on which version of gcc is installed
in the target distro), IOW it's totally fine for only one version to be
available.
With this package in the past they ma
On Tue, Dec 29, 2020 at 09:19:17PM +, FreedomBen via devel wrote:
> rpmlint complains (which I fully expected from reading the packaging
> guidelines) about my spec file being named "pick-v4.0.0.spec" instead of
> "pick.spec".
> What's the best way to manage spec files for different versions?
I think it's entirely up to you.
The source tree in Fedora uses "main" for the Rawhide version of the
package and f32, f33, etc. for releases. Also, the %changelog in the SPEC
file is in a way an immediate history of the SPEC file, including
versioning and revisions.
I usually keep external SPEC
rpmlint complains (which I fully expected from reading the packaging
guidelines) about my spec file being named "pick-v4.0.0.spec" instead of
"pick.spec".
What's the best way to manage spec files for different versions? git tags in
the repo? directories with version info? something else?
Ben
On Mon, 28 Dec 2020 at 21:12, FreedomBen via devel <
devel@lists.fedoraproject.org> wrote:
> Hi all,
>
> I've read a crap ton of pages now about package creation/maintenance but
> feel like I'm missing stuff and spinning wheels so I wanted to ask. The
> process seems pretty muddled :-D
>
> I've g
