On Fri, Jan 21, 2022 at 08:44:14PM +0100, Marc Espie wrote: > On Fri, Jan 21, 2022 at 07:47:44PM +0100, Stefan Sperling wrote: > > On Fri, Jan 21, 2022 at 07:24:34PM +0100, Marc Espie wrote: > > > On Fri, Jan 21, 2022 at 07:06:22PM +0100, Stefan Sperling wrote: > > > > I never understood why new ports have to submitted as a tarball. > > > > Why not accept new ports as a diff which only creates new files? > > > > It is trivial to create such a diff. > > > > > > Give me the magical recipie that does NOT create directories in the actual > > > CVS repository/is usable without write access to the OpenBSD CVS repo or > > > a copy ! > > > > > > They DON'T create new files, they create NEW DIRECTORIES. > > > > > > Unless I'm missing something, CVS makes it NEXT TO IMPOSSIBLE TO DO > > > without a local repository! > > > > cvsdo can do it by faking new directories entries in CVS/Entries files. > > This does not require adding directories to the repository (see below). > > I am not suggesting this is a great solution, but it can be done. > > Is this documented anywhere for new people?
I doubt it. But before recommending this approach, a few people should try to work through entire submissions of non-trivial ports with it. There might be some gotchas which the trivial cases I've used this for cannot uncover. I last used cvsdo years ago while submitting diffs for both src and ports, and only in the rare cases where I had to add new files. Nothing like tor-browser or chromium :P Nowadays, I would use devel/got to create such a diff against ports.git cloned from github. But that is not CVS and it is probably too early to generally recommend got instead of git to work on ports. Though I would be happy to receive bug reports against got from interested ports devs.
