On Mon, Jun 12, 2017 at 5:34 PM, Tom Stellard <tstellar@xxxxxxxxxx> wrote: > On 06/12/2017 05:22 PM, Matthew Miller wrote: >> On Mon, Jun 12, 2017 at 05:01:19PM -0400, Tom Stellard wrote: >>> 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 >> >> You'll have to install the devel package at the same time you update to >> the new version of the base package. (Fortunately, DNF now again >> follows the yum convention of translating install to upgrade when you >> are asking to install an updated package. >> >> > > The old base package: 'llvm' is being deprecated and is being moved > into 'llvm4.0' as a sub-package. For example: > > Before: > +llvm > - llvm > - llvm-devel > - llvm-libs > - llvm-static > - llvm-doc > > After: > > + llvm (deprecated) > > +llvm4.0: > -llvm4.0 > - llvm4.0-devel > - llvm4.0-libs > - llvm > - llvm-devel > - llvm-libs > - llvm-static > - llvm-doc > Why? What's the compelling reason to do this? And if we're doing this to llvm, are we going to do this to gcc, too? -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
