[PlanetCCRMA] State of Fedora 26 repo

Yury Bulka setthemfree at privacyrequired.com
Sun Oct 22 01:25:25 PDT 2017

Let's take SuperCollider as an example. It is included in debian main,
so it probably wouldn't have any licensing issues with fedora.

How the process of moving it into main fedora would look like in

Take the srpm, adapt it to Fedora's Packaging Guidelines [1] and submit
to fedora?

Then, I guess, the person doing it would have to take the responsibility
of maintaining the fedora package.

I could try doing it maybe, although I don't have much experience in
packaging or C++ development. Is the knowledge of C++ absolutely
required to be able to maintain a fedora package for SuperCollider?

[1]: https://fedoraproject.org/wiki/Packaging:Guidelines

Martin Tarenskeen <m.tarenskeen at zonnet.nl> writes:

> On Sat, 21 Oct 2017, Yury Bulka wrote:
>> Dear all,
>> I haven't posted here before, but after reading this list for a while
>> I have an impression that we seem to expect too much work from a
>> single person (Fernando) - providing -rt packages of the kernel,
>> maintaining planeccrma repos, as well as maintaining fedora packages for
>> supercollider and a whole bunch of other software...
>> I'm thinking that maybe we could somehow distribute this work?
>> For instance by trying to move *some* of the packages (like
>> supercollider) from planetccrma to main fedora repos?
>> How hard may that be? Is there anything about, say, supercollider, that
>> would not allow it to be included in main fedora?
> Several packages that used to be part of PlanetCCRMA are now part of
> the normal Fedora repos already. Due to, among others, Fedora's strict
> licencing policy not all PlanetCCRMA packages could/can be moved to
> Fedora though.
> Fernando does a tremendous job maintaining the PlanetCCRMA packages. I
> totally agree that it would be great if he got some help from others.

More information about the PlanetCCRMA mailing list