Bug 1119848 - Shouldn't new chroot be also selected default?
Summary: Shouldn't new chroot be also selected default?
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-15 16:13 UTC by Parag Nemade
Modified: 2014-07-16 04:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-15 16:57:09 UTC


Attachments (Terms of Use)

Description Parag Nemade 2014-07-15 16:13:23 UTC
Description of problem:
Some of my projects was having chroots for f20 and rawhide. With the addition of f21 chroot now, I am thinking if its possible to automatically enable f21 repo for such projects also?

Comment 1 Miroslav Suchý 2014-07-15 16:57:09 UTC
I do not think so. What about e.g EL7? Should we have enabled it as well when we recently added it? But what if user is interested only about Fedora and not RHEL? And vice versa.
Additionally building for aditional chroot consume additional resources. And if user is not really interested, why we should enable it?
Clicking twice per year to enable new chroot is really minimal effort for user.

Comment 2 Parag Nemade 2014-07-16 04:18:15 UTC
Okay. No issues.


Note You need to log in before you can comment on or make changes to this bug.