Re: Sysadmin Load Reduction: Code Related Services
On Mon, Nov 18, 2019 at 7:33 PM Ben Cooksley wrote: > > On Tue, Nov 19, 2019 at 7:27 AM Albert Astals Cid wrote: > > > > El dilluns, 18 de novembre de 2019, a les 13:34:19 CET, Harald Sitter va > > escriure: > > > And lastly, fold the i18n data into the yaml. > > > > So to know which is the stable i18n branch of okular i have to checkout > > it's master branch, read a file and then change to whatever branch it is > > said there to be the stable branch? > > > > Feels a bit weird that the master branch has that kind of knowledge to be > > honest. > > I think Harald was referring to the 'metadata.yaml' files in > sysadmin/repo-metadata in this case. Yep.
Re: Sysadmin Load Reduction: Code Related Services
On Mon, Nov 18, 2019 at 6:29 PM Ben Cooksley wrote: > It'll be hard to tell whether a name is unique or not when creating a > repository unfortunately. > For the most part I do not expect collisions to occur though and we > certainly won't aim to create duplicate names. Wouldn't creating a repo also include creating the repo-metadata file for it? Through that it should be easy to assert uniqueness via a server-side hook on repo-metadata. In point of fact, if we fully flatten out the files I expect uniquness would be implicit. e.g. repo-metadata/projects/blinken.yaml (repopath: kde/blinken) repo-metadata/projects/kinfocenter.yaml (repopath: kde/kinfocenter repo-metadata/projects/www-kde-org.yaml (repopath: sysadmin/www-kde-org) HS
