UMD REPO Team Issues

From EGIWiki
Jump to: navigation, search

Based on the CAs exercise, a couple of YUM/APT related issues came up to me that need to be clarified:

First of all, there are three "types" of releases identified until now:


Concerning the YUM/APT repos (re)creation

We see two cases:

Case A & C: no special actions have to be performed by the Repository respectively to the YUM/APT repositories creation. If the SW provider includes the repodata folder(s) in the bundle, then the SW will be provided by the Repository, in a YUM and/or APT form. The only action that actually has to be made by the Repository is to change the "baseurl" value withn the given (by the SW provider) .repo files. NOTE: In case "we" want the rpms/deb to be digital signed, the repodata/Packages.gz should be recreated (overwriting the ones that SW provider provided).

But, when the release goes into production repo it should be appended to the rest of the packages.

In this stage the YUM and/or APT repos should be (re)generated. I am putting the "(re)" into parenthesis because there are two possible subcases here:

      In the case of B.1: the YUM/APT repos should be regenereted, replacing the old ones.
      In the case of B.2, the YUM/APT repos provided by the SW provider should be used "as is".

One more action that has to be made by the Repository, is to change the "baseurl" value withn the given (by the SW provider) .repo files. NOTE: In case "we" want the rpms/deb to be digital signed, the repodata/Packages.gz should be recreated (overwriting the ones that SW provider provided).

     once every major release? (NOTE: in this way, he/she will not be able to change the schema, until the submission of the next major release)


--Kkoum 17:14, 28 September 2010 (UTC)

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export