IMO, the latest package should be always non-versioned one and versioned should be only the compat packages. E.g. the llvm package is always the latest, shipping llvm 4.0 ATM and llvm3.9 should be compat package, shipping the previous version. Once new version is released, lets say llvm 5.0, the non-versioned llvm should be migrated to that version and compat llvm4.0 should be introduced. I tried to propose such guidelines a while ago [1] but failed, although there was general consensus that this should be the way. So if I may suggest, please don't introduced llvm4.0 yet. Vít [1] https://pagure.io/packaging-committee/issue/227 Dne 12.6.2017 v 23:01 Tom Stellard napsal(a): > Hi, > > I'm working on moving the llvm-devel sub-package from the llvm package to > a new llvm4.0 package, however, when I upgrade from the llvm sub-package > to the llvm4.0 sub-package, I am getting file conflicts. > > This can be reproduced on rawhide with these commands: > > [root@746864b6a202 /]# dnf install llvm-devel > [root@746864b6a202 /]# dnf install 'dnf-command(copr)' > [root@746864b6a202 /]# dnf copr enable tstellar/llvm-versioned > [root@746864b6a202 /]# dnf install llvm-devel-4.0.0-13.fc27 > > Here is the error: > > Error: Transaction check error: > file /usr/include/llvm from install of llvm-devel-4.0.0-13.fc27.x86_64 conflicts with file from package llvm-devel-4.0.0-4.fc27.x86_64 > file /usr/include/llvm-c from install of llvm-devel-4.0.0-13.fc27.x86_64 conflicts with file from package llvm-devel-4.0.0-4.fc27.x86_64 > > I don't understand how a package can conflict with on older version of > the same package. Here are the spec files: > > llvm-devel-4.0.0-13.fc27.x86_64: http://copr-dist-git.fedorainfracloud.org/cgit/tstellar/llvm-versioned/llvm4.0.git/tree/llvm4.0.spec > llvm-devel-4.0.0-4.fc27.x86_64: https://src.fedoraproject.org/cgit/rpms/llvm.git/tree/llvm.spec > > Is this a bug in dnf/rpm or am I doing something wrong with the spec files? > > > -Tom > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
