#16: Create Installer repo test(s)
--------------------------+-------------------------------------------------
Reporter: jlaska | Owner: rhe
Type: task | Status: new
Priority: minor | Milestone: Fedora 13
Component: Test Review | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment (by rhe):
Replying to [comment:17 jlaska]:
> Replying to [comment:16 rhe]:
> <skip>
> One suggestion I might offer is to relocate the test repository to a
subdirectory underneath your main ~/public_html. Just so you have room to
add other content without cluttering up the data used for this test.
>
Yeah, thanks for reminding me.
> Another thought, definitely above and beyond the original call for this
ticket, what are your thoughts on providing several packages in your
sample repo? I'm wondering if it would make sense to include several
different packages each tagged differently in your XML file. For example
...
> * <packagereq type="default">kong</packagereq>
> * <packagereq type="optional">wife-of-kong</packagereq>
> * <packagereq type="mandatory">mother-of-kong</packagereq>
> * <packagereq type="conditional" requires="wife-of-kong">daughter-of-
kong</packagereq>
>
> Okay, I'm having fun with the names, but what do you think?
There's no bad side about this, so I added them. But I don't think we need
to check the packages with different types too carefully in new repo.
since the existing repo can also check these. If the new repo packages can
be listed and installed correctly, that's ok.
[https://fedoraproject.org/wiki/QA:Testcase_Additional_Http_Repository
http_repository] has been updated regarding this. Do you have any other
concerns? Thanks.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/16#comment:18>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
