Hello, * On Wed, Feb 24, 2021 at 10:29:53AM -0500 David Sugar wrote:
from what I recall, in a debian environment, the .dsc file is normally always "generated" from the debian/control file,
correct.
OBS uses a .dsc alone much like it were a rpm .spec that can be hand edited, and this is a great convenience. I can build a .dsc without having any debian tools on a non-debian platform (alpine linux, for example), and feed that into obs to get debian package builds.
It might be a convenience for people who do not have a debian platform, but for sure, only for them. For users on a Debian platform, it is a PITA to perform this double-housekeeping. What contents does the .dsc have that OBS needs from it, and not from debian/control? To be honest, I do not see anything. What I am doing: Whenever I do any significant change to the control file, I run the build on a Debian, extract the resulting .dsc and put it into obs. Straight-forward, isn't it?
I now actually have my own scripts that generate a obs valid .dsc (which is really a subset of debian) from the control file for me,
I have thought about it myself, too, but I was not sure what I really need for this. If this is really possible, then debian/control must contain all necessary information, mustn't it? So, why does OBS need the .dsc in the first place? BTW, can you share your script(s)? ;) Regards Spiro. -- Spiro R. Trikaliotis https://spiro.trikaliotis.net/