On 4/27/20 10:34 PM, Kyle Edwards wrote: > On Sat, 2020-04-25 at 20:31 +0200, Thomas Goirand wrote: >> If the library you need to package isn't needed by any other package, >> simply apply the needed patch and upload. Even better if it's only a >> build-dependency, in which case it wont ever be a problem. > > This brings up an interesting question: are things that are build- > dependencies only covered by the no-vendoring rule?
Of course yes. Otherwise, we would leave all Go stuff vendored and never care, for example. > In my case, I *am* upstream. So, for example, we forked enet and made > some changes to how it works. In that case, I could make a new package > called adios2-enet or ornl-enet, and depend on it for ADIOS. Is that > correct? That's IMO the recommended way, yes. Thomas Goirand (zigo)
