New subject: [Bug 2217968] Review Request: tbb2020.3 - Create compatibility package for tbb2020.3

27 Jun 2023

      https://bugzilla.redhat.com/show_bug.cgi?id=2217968
Bug ID: 2217968
           Summary: Review Request: tbb2020.3 - Create compatibility
                    package for tbb2020.3
           Product: Fedora
           Version: rawhide
          Hardware: All
                OS: Linux
            Status: NEW
         Component: Package Review
          Severity: medium
          Priority: medium
          Assignee: nobody@fedoraproject.org
          Reporter: codonell@redhat.com
        QA Contact: extras-qa@fedoraproject.org
                CC: package-review@lists.fedoraproject.org
  Target Milestone: ---
    Classification: Fedora
Spec URL: https://src.fedoraproject.org/rpms/tbb/raw/rawhide/f/tbb.spec
SRPM URL:
https://kojipkgs.fedoraproject.org//packages/tbb/2020.3/17.fc39/src/tbb-2020...
Description: Create a compat package for legacy tbb.
Fedora Account System Username: trodgers
As part of the process of modernizing TBB in Fedora:
https://fedoraproject.org/wiki/Changes/F39ModernizeTBB
We need to create a compat tbb package e.g. tbb2020.3 which is going to be used
by existing applications.
The existing tbb will move forward with the newer OneTBB API.
I'm filling this on behalf of Thomas Rodgers to start the ball rolling to
create the tbb2020.3 repository.
This meets the Package Review Process exception:
~~~
The package is being created so that multiple versions of the same package can
coexist in the distribution (or coexist between EPEL and RHEL). The package
MUST be properly named according to the naming guidelines and MUST NOT conflict
with all other versions of the same package.
~~~
Likewise for naming the package:
~~~
Version numbers used in compat libraries do not need to omit the dot . or
change it into a dash - (see Multiple packages with the same base name for more
info on this case).
~~~
So we use the "2020.3" version in the name as "tbb2020.3"
If we need a tbb2020.3.spec and srpm to create the repo then can make that
available, but making the initial import be based on tbb lets us have a record
of the evolving changes from tbb onwards.
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2217968

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report...

[Bug 2217968] New: Review Request: tbb2020.3 - Create compatibility package for tbb2020.3