Bug 25999

Summary: Make porting of programs to Mageia easier by replacing the name of a required dependancy with a specific .so file from it
Product: Mageia Reporter: Kristoffer Grundström <lovaren>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Kristoffer Grundström 2020-01-01 04:12:23 CET 
Description of problem: I came to think that it would be a lot easier if we in the future could switch from using a specific package name as a buildrequire to type a specific .so file or similar from it to make urpmi find the requirements faster. Lets say you port package A from Ubuntu or Debian and the package is named differently in those distros than what Mageia calls it.

Now's the time to change the field in the spec file called BuildRequires: Package A to file.so.

When you then download the spec file and use urpmi to install the package that holds this file urpmi will find it.

That way you don't have to manually look everytime if Mageia has the right package or not.

Version-Release number of selected component (if applicable): 4.14.2.1
Comment 1 Lewis Smith 2020-01-01 19:23:24 CET 
Looks like a suggestion to overcome different package naming in different distributions. Not sure what package(s) would be involved.
I cannot see this happening, but assigning to Thierry for comment.

Source RPM: rpmbuild => (none)
Assignee: bugsquad => thierry.vignaud

Comment 2 Thierry Vignaud 2020-01-01 21:23:11 CET 
That's why we're using "pkgconfig(foobar)" BRs when we can…

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX