2014-09-18 22:14 GMT+04:00 Marc Espie <es...@nerim.net>: > On Thu, Sep 18, 2014 at 09:30:42PM +0400, Vadim Zhukov wrote: >> The bsd.port.mk's dump-vars always prints >> SUBPACKAGE=whatever-is-default-for-the-current-port value. Which is, >> actually, useless. Then this value gets into sqlports directly. Making >> SUBPACKAGE field totally useless as well. >> >> Options I see: >> >> a) Get rid of SUBPACKAGE in dump-vars output and sqlports; >> b) Tweak bsd.port.mk (this will result in very dirty hack); >> c) Tweak sqlports to override SUBPACKAGE by actual value taken from >> FULLPKGPATH. >> >> I'd go with (c), even if it will denormalize database it - >> "SUBPACKAGE" is much easier and less prone to type than >> "SUBSTR(FULLPKGPATH, INSTR(FULLPKGPATH, ',-')+1)". Any opinions? > > Having the default SUBPACKAGE in there is intentional, actually.
Out of curiosity, what's it? > You've got the FULLPKGPATH in ports and the PATHS table if you need to parse > the information related to a specific SUBPACKAGE. I agree that info is already there; I just can't understand the benefit of current SUBPACKAGE values in "Ports" table. -- WBR, Vadim Zhukov
