On Fri, 18 Dec 2020 03:48:17 +0100 [email protected] wrote: > Hi GNUtoo and all, Hi,
> I can't remember the content of the GitLab RSS Panel, but cgit does > provide Atom commit feeds, i.e. > https://git.replicant.us/contrib/GNUtoo/www.replicant.us/atom/?h=master > > These doesn"t work with the WP Panel or doesn"t contain the desired > content? Thanks for pointing that out: my commit message doesn't contain enough information on why it is broken exactly. For instance I could change that: > When migrating away from GitLab (mainly due to too heavy resources > consumption) to cgit, the git RSS feed stopped working as cgit > doesn't generate an RSS feed. > > While it's probably possible to deploy some software like > git2rss[1] to restore that functionality, we still haven't > deployed and configured such software. to that: > When migrating away from GitLab (mainly due to too heavy resources > consumption) to cgit, the git RSS feed stopped working. As cgit > doesn't generate an unified RSS feed, it cannot be fixed simply > by changing the feed URL. > > While it's probably possible to deploy some software like > git2rss[1] to add back an unified RSS feed, we still haven't > deployed and configured such software. What do you think of such changes? As far as I know, having an unified feed is not possible with cgit, but I'd be really happy to be wrong on that as having a feed of git changes looks looks really useful. As for using a single repository feed, it's not really an option as with our current setup, there is no single repository that is modified at each changes or group of changes. For instance we have a manifest repository that is used to define what repositories to use, but the repositories we modify use branches, so we cannot track the changes from that manifest repository. Most of the time, there is a lot of activities in the branches of various repositories but none in the manifest repository. The rationale behind not using fixed revisions in the manifest is to reduce the amount of work: - We sometime need to rebase that repository, for instance when making a new release for a given Replicant version. Not modifying each single line make that much more easy. - Having to modify the manifest repository for each single change would be way too much time consuming and error prone. In contrast, most GNU/Linux distributions typically have a one or very few git repositories that store package definitions with fixed revisions. So that would have been possible in cases like that. Denis.
pgpiAUksXKbjS.pgp
Description: OpenPGP digital signature
_______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
