@stormi said in git repository structure and conventions for RPMs:

The repository name must match that of the source package.

A you really shure you want a repo for every source package?

It could be hundreds of repos! And you would need to make snapshots/synchronizations for making xcp-ng releases among all of them.

And it could lead to situation, when you need to reimport some new history for some abandoned and resurrected package.

While having one more level of indirection is not a fun either, not having it seems a bit restrictive.

@stormi said in git repository structure and conventions for RPMs:

The repository name must match that of the source package.

A you really shure you want a repo for every source package?

It could be hundreds of repos! And you would need to make snapshots/synchronizations for making xcp-ng releases among all of them.

And it could lead to situation, when you need to reimport some new history for some abandoned and resurrected package.

While having one more level of indirection is not a fun either, not having it seems a bit restrictive.

I suspect, that a default build in DDK would lead to more or less xenserver binaries, not xcp-ng, isn't it?

Oh, Wednesday would be nice (it is not urgent in any way).

However, I should note, that it is possibly not only for that my need: it could be a GPL violation to publish rpms from a modified .spec without publishing .spec.

Good day.

I'm trying to apply that patch https://lists.gt.net/xen/devel/432779 to xen-hypervisor, and at first looking for it's spec to rebuild.

Could you please point me out where is the current one lying? I've found one at github.com/xcp-ng/xcp/ , but it is 4.7.4-4.1 , and updates from https://updates.xcp-ng.org/7.4/ got me xen-hypervisor-4.7.5-4.4.x86_64 and also suggests xen-hypervisor-4.7.5-5.2.x86_64 .