On Mon, 02 Mar 2020, Theo de Raadt wrote: > Can't we assume bird1 will go away eventually?
Yes, sooner or later. Likely later for OpenBSD when looking to net/bird/1 and net/bird/2 co-existence, thus ongoing BIRD 1.x compatibility might be more important for OpenBSD than for rpki-client downstreams such as Fedora (which only ships BIRD 2.x). And I expect I[SX]Ps to be quite conservative, too. Could maybe somebody with real-world insights comment on this, please? > Or why don't those people convert json to their required format -- make > it their problem? Are you referring to BIRD 1.x or 2.x here? I would prefer native BIRD 2.x compatibility rather having to convert json around. Nevertheless, I'm not sure if it's fair to remove the BIRD 1.x compatibility (which is currently broken anyway). > The idea is you can specify many outputs. That will make the commandline > very long, especially for the way we run it in cron. Oh! I'm sorry, I didn't see the idea of specifying many outputs. On Mon, 02 Mar 2020, Theo de Raadt wrote: > btw, in almost all other commmands -o (along with -f) indicates an filename, > not a format. > > So that isn't the letter you want. Personally, I do not care about the letter for the option, that was just a quick example to explain my idea. > As written today with mkstemp + unveil/pledge, each output format > function can only output one file. Using one format name to create > multiple outputs is going to require some restructuring. I see. Honestly, my downstream needs would be satisfied with "-B" leading to BIRD 2.x compatible output only (avoiding new options and restructuring), but I don't want to behave like a bull in a china shop. Thus in the end it's your decision as upstream... Regards, Robert
