Re: How to handle a forked project

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "DJ" == David Juran <david@xxxxxxxx> writes:

DJ> So now my question is, what is the procedure for switching the code
DJ> base for the Fedora package from Vuze to BiglyBT?

Since you're dealing with what's basically a new project, just submit a
new package review.  Once it's in, you can have the new package obsolete
the old one in accordance with
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-replacing-existing-packages

Then you can retire the old package.

DJ> Do I just switch the tar-ball in the azureus package repo and add an
DJ> "obsoletes" statement in the spec-file?

You shouldn't; that kind of lies about what software the repository
contains.  The old project could come back to life at any time and it's
certainly possible for both projects to coexist.

DJ> Can I change the name of the source rpm?

That's fixed from the name of the repository.

DJ> Can the name of the entire package (including the package git
DJ> repo and bugzilla entry) be changed?

No, that's fixed.  Creating a new package and having it replace the old
one is the proper way.

 - J<
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux