On Sat, Jul 14, 2018 at 04:45:42PM +0300, Vadim Zhukov wrote: > сб, 14 июл. 2018 г. в 16:10, Stuart Henderson <[email protected]>: > > > > On 2018/07/14 16:07, Vadim Zhukov wrote: > > > I've got a package from mirror, which had tor files under /etc/rc.d/, > > > and acted accordingly. Yes, the system wasn't very fresh, my bad. > > > > There have been big changes in package tools recently - using old tools > > with current packages *will* break things. > > > > > Am i > > > right that using "new" package (where @rcscript at the top is okay) > > > with "old" pkg_add works by accident? > > > > They don't really work as you have seen ;) > > Then I backout my change. But there would be others after me, for > sure, who'll fill root partition by running pkg_add... There is > "global system version" but it only triggers updates, but doesn't tell > "you can't install this package without updating tools first". What > about making version in "pkg_create -V" look like "major.minor" with > same semantics like we have with shared libraries? E.g.:
Rules are simple, -current is -current. I allowed for some leeway before letting @rcscript move to its proper location. The commit that fixes rcscript is revision 1.251 of PackingElement.pm, dated 2018/05/26. *anyone* who's using an older base snapshot and wants -current packages is asking for trouble. Heck, all the define-tag/tag stuff was not fully working until a week ago.
