Custom package extension?

[pwFoo]

Would it possible to change the package extension from *.tar.gz for example to *.gpm?
Maybe as option or with a config file?

[JMLX42]

Would it possible to change the package extension from *.tar.gz for example to *.gpm?
Maybe as option or with a config file?

Our philosophy is to use existing technologies/standards as transparently as possible.

We don't see the point of creating new file extensions if they don't convey any specific semantic or features. It's just confusing.

[pwFoo]

Idea behind a custom extension was easier separation of gpm packages from tar.gz archives.
So I could add some sources including tar.gz files to gpm repository without matching git-lfs track pattern.

[JMLX42]

I see. The way we designed it, GPM-compliant git repositories don't store non-GPM-compliant files.

I guess the current implementation won't mind either way.

I'll give it some thinking. Maybe something like .gpm.tar.gz.

[pwFoo]

It would be just a nice to have! Not a must have to me...
Optional gpm.tar.gz would be fine too.

[Flydroid]

Hi,

GPM sounds amazing, pretty much exactly what we have been looking for to manage releases and dependencies.
Except we already have a package file which does have a custom file ending ".nipkg". This package file just packages two other tar.gz files and a manifest file.

[JMLX42]

GPM sounds amazing, pretty much exactly what we have been looking for to manage releases and dependencies.
Except we already have a package file which does have a custom file ending ".nipkg". This package file just packages two other tar.gz files and a manifest file.

@Flydroid PR welcome 👍