On 2/4/21 11:19 AM, Fabio Valentini wrote:
> I am aware of at least three (?) other "noteworthy" packages that have
> to deal with this (or at least, had to do something like this in the
> past):
>
> - ruby (with the gems that are bundled with the interpreter),
> - perl (with the modules that are
Dne 04. 02. 21 v 20:19 Fabio Valentini napsal(a):
On Thu, Feb 4, 2021 at 7:24 PM Artur Frenszek-Iwicki
wrote:
The Lazarus package currently builds three RPMs: "lazarus", which contains the IDE, and the
"qt5pas" library, along with "qt5pas-devel".
qt5pas is, technically, a separate project wit
On 04/02/2021 19:48, Miro Hrončok wrote:
So the ver-rels are:
main: 1.2.3-1.fc34
foo: 7.8.9-1.2.3^1.fc34
Once the base_release is bumped:
main: 1.2.3-2.fc34
foo: 7.8.9-1.2.3^2.fc34
And once the main version is bumped without foo, base_release back to 1:
main: 1.2.4-1.fc34
foo: 7.8.9-1.2.
On 04. 02. 21 20:19, Fabio Valentini wrote:
Some handle situations like these by setting Version for each
subpackaged component separately and only ever incrementing Release
and never resetting it to 0.
In the past, I've done:
Version: 1.2.3
# rpmdev-bumpspec will bump this:
%globa
On Thu, Feb 4, 2021 at 7:24 PM Artur Frenszek-Iwicki
wrote:
>
> The Lazarus package currently builds three RPMs: "lazarus", which contains
> the IDE, and the "qt5pas" library, along with "qt5pas-devel".
> qt5pas is, technically, a separate project with its own versioning - but
> since its distri
On Thu, Feb 04, 2021 at 06:58:15PM -, Artur Frenszek-Iwicki wrote:
> The library provides Qt5 bindings for applications developed using
> Lazarus, so being broken into a subpackage allows for dependent packages
> to pull in only the library, instead of the whole IDE.
Ah, I see.
It might reall
The library provides Qt5 bindings for applications developed using Lazarus, so
being broken into a subpackage allows for dependent packages to pull in only
the library, instead of the whole IDE.
___
devel mailing list -- devel@lists.fedoraproject.org
To
I am not the maintainer of the package, but I am aware that there are
two sources with two versions here:
https://src.fedoraproject.org/rpms/python-pyasn1/blob/f33/f/python-pyasn1.spec
The sub-package ends up with a provides with the modules version:
# rpm -q --provides python3-pyasn1-modules
p
On Thu, Feb 04, 2021 at 06:37:12PM -, Artur Frenszek-Iwicki wrote:
> Same tarball, separate versions. Dependency is one-way.
Well, that's annoying. I guess the next thought is: is there any point in
having the bundled library actually broken out into a subpackage, or should
it just be hidden a
Same tarball, separate versions. Dependency is one-way.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-
On Thu, Feb 04, 2021 at 06:24:37PM -, Artur Frenszek-Iwicki wrote:
> The Lazarus package currently builds three RPMs: "lazarus", which contains
> the IDE, and the "qt5pas" library, along with "qt5pas-devel". qt5pas is,
> technically, a separate project with its own versioning - but since its
>
The Lazarus package currently builds three RPMs: "lazarus", which contains the
IDE, and the "qt5pas" library, along with "qt5pas-devel".
qt5pas is, technically, a separate project with its own versioning - but since
its distributed alongside Lazarus, and Lazarus depends on it, it made sense to
b
12 matches
Mail list logo
