Playground Repo Requirements Document

Alek Paunov alex at
Tue Mar 4 19:10:35 UTC 2014

On 04.03.2014 16:02, Honza Horak wrote:
> On 03/04/2014 02:01 PM, Tadej Jane┼ż wrote:
>> On Mon, 2014-03-03 at 12:16 +0100, Honza Horak wrote:
>>> 4) We have a stack of packages that I want to deliver to Fedora users,
>>> but the stack would update some packages from Fedora base repo and/or we
>>> do not want to use SCLs. Then we can get a Copr repository as a RPM
>>> package and include this RPM in the Playground, so people installing
>>> this RPM package would actually say: "Yes, I want to enable these
>>> packages and I agree to get some of my Fedora-base packages updated".
>> Well, this is certainly a creative idea, but I currently have mixed
>> feelings about it. What's the gain in creating a RPM package with
>> the .repo file and somehow telling the user what will happen (e.g. "Be
>> warned, some Fedora packages from the main repo will get updated"),
>> compared to just pointing users at a COPR repo with the appropriate
>> description on its web site?
> Right, I don't remember which use case I had on my mind with the 4th
> point, so let's just stay with the 1, 2 and 3 ;)

I think, I have a real use case: Samba AD - The AD functionality is 
disabled in Fedora proper, due to the incompatibility between the 
bundled (heimdal) and system MIT Kerberos implementations.

The incompatibility is dangerous in the general case, but is harmless 
when e.g. Samba will be deployed as a single server in container or 
dedicated instance. OTOH, AD functionality is very good selling point 
:-). Possible solution: Samba with enabled AD in COPR, reviewed Samba AD 
.repo package in Playground.

Why in the Playground? - Discoverability. How otherwise the user will 
find that given COPR? How to choose between several alternative COPRs?

Yes, we do not have UX centric package searching tools (possibly except 
apps.fp.o/packages up to some degree), but we have amounts of priceless 
data - the rest is a matter of reasonable platforms and work and will be 
here someday :-)

I think we could generalize - .repo in the Playground - 2-steps 
(enabling playground + installing the .repo) easy mechanism to change 
the sane defaults of the system for these who know what they doing or 
just want to experiment.

Kind regards,

More information about the env-and-stacks mailing list