On Thu, Jun 28, 2018 at 06:55:45PM -0300, Elias M. Mariani wrote: > Hi Mark, > Maybe I missed the mail or something, but could you also comment about > the new "@tag" thingy that I saw working on ? > I'm just porting LXQt and I see that is related for example with the > desktop updates. > > Cheers. > Elias.
Yeah, portcheck will now do the right thing. Basic current mechanism is discussed in pkg_create(1) I wrote an email you can find on the ports archive recently. @tag update-desktop-database for now. I'm slowly converting other @exec remnants that apply to it. The idea is to make packages "extensible" to new directories and file types (we do have builtin support for @lib/@font/@info/@man...) @tag are actually annotations that may be related to current context (like for @exec, tags can be linked to the most recent file/directory) and are meant to be used to give extra semantics to package contents that are related to another installed package. For now, only @define-tag update-desktop-database at-end %D/bin/update-desktop-database ... @tag update-desktop-database is used, but there lots more at-end @define-tags on the way, and more semantics for later. Eventually, it should replace most @exec/@unexec in the ports tree to something better. RPMs has a global mechanism that serves similar purposes (triggers) but the semantics is completely different, and I hope that @tags will prove to work better :)
