proposal: decide on VERSION markers and DESTDIR

[git-bruh]

DESTDIR seems mostly useless to me, but VERSION and other markers have a valid use case shown here in kiss-xorg: https://github.com/ehawkvu/kiss-xorg/tree/master/xorg/libXmeta

It can also be helpful to prevent patch failures if someone is using patch files to add something to sources and build without duplicating the whole package

[aabacchus]

I sometimes curl $(cat pkg/sources); VERSION is unhelpful for this.

[ghost]

I am for explicitly specifying DESTDIR (with its removal from kiss) and against MARKERS (for the reason mentioned above). But really, I don't care C:

[Vouivre]

I have the same opinion as @nvidialinuxuser . When I explicitely specify DESTDIR, I know exactly the content of
the variable. It would be convenient with markers, but I prefer without.

[ioraff]

Maybe also relevant are the implicit RUSTFLAGS, GOFLAGS, and GOPATH

[aabacchus]

Maybe also relevant are the implicit RUSTFLAGS, GOFLAGS, and GOPATH

Agreed. Explicit is better than implicit.

[git-bruh]

👍 to remove DESTDIR, RUSTFLAGS, GOFLAGS, GOPATH, and VERSION markers
👎 to keep them

[echawk]

For clarification - I'm totally fine with removing the implicit environment variables, just not the VERSION markers.

[git-bruh]

@ehawkvu Btw your use case can also be accomplished with a script that does the same thing kiss does for substituting variables but at commit-time

[echawk]

@git-bruh - I don't doubt the ability of git hooks to replicate the way things currently work, but I've never intereacted with them. Have you done something similar, or a POC?

@cemkeylan - What's your solution with Carbs? IIRC there was a pr/issue where you had mentioned what you do.

[cemkeylan]

I've been against this functionality since day one. It kills the entire "static" package management aspect. Instead of building such a functionality inside cpt I use some personal scripts along with m4 macros. These can be used to create boilerplate build templates (e.g. for go packages), dependencies (e.g. meson when using a meson template), and sources (such as gnome projects or Xorg software).

[git-bruh]

https://codeberg.org/kiss-community/repo/issues/90