Is it possible to not show all of the licenses ?

[freedomtrain]

Is it possible to not show all of the licenses ?

Thanks

[lafriks]

I don't think so but you can set PREFERRED_LICENSES in app.ini that will be shown on top in select box

[freedomtrain]

Thanks !!!!
Are the licenses entries hard coded ?
I deleted all of the licenses files that we do not want to show as an option and they still are showing up

[lafriks]

They are compiled in binary. So to remove them you would have to recompile from source

[freedomtrain]

Ah ha ......
Thanks !!!! Is there any documentation on how to recompile my current build from source ?

[sapk]

We have custom licenses, as stated in docs here, but the behavior is to extend the default one not replace them.

To compile the exact same build you need a golang env ready and follow https://docs.gitea.io/en-us/install-from-source/.
To know the commit/banch/version of binary use ./gitea -v of your current version. It will also display TAGS used to build the binary like sqlite or bindata

[sapk]

And I forget, if you find any bottleneck following the documentation, feel free to contribute to https://github.com/go-gitea/docs and ask question on Discord or here. 😉

[freedomtrain]

I have have followed the instructions here https://docs.gitea.io/en-us/install-from-source/
The license that I have deleted are still showing up.

Are they in bindata ?

[sapk]

For context, bindata (more exacly go-bindata) is a program that convert file in go source code accessible like a filesystem.
Generated code should be under module/options. try to do a make clean, remove file under options/license that you don't want, and do make generate build with your tags.
You could also try without bindata tag but you will need to keep around static file like /templates or /public to work.

[lafriks]

As a feature this should be implemented in the future to be able manage licenses

[sapk]

One easy way could be to not use default licence if custom/licenses are used ? or add an option to not use default.

[BjoernAkAManf]

I was looking for something similar. How about a special file inside the license (or other overriding) folder like .INCLUDE or .EXCLUDE to specify included or exclude licenses respectively? It would be a shame to maintain a separate set of licenses just to remove some defaults.

[strk]

Pull request adding documentation for PREFERRED_LICENSES: #3230

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[wolftune]

I think it would be preferable to indeed have a shorter list. At the least, showing all versions of licenses (such as even CC-BY 1.0 and 2.0 and 2.5 etc) is really noisy. If someone is actually going to use obscure or outdated licensing or is importing an old repo, they can do that without using the dropdown menu in creating new repos.

I would urge that a shorter list be used in general even for the relatively complete set. And it would be nicest to have a default of showing only the PREFERRED_LICENSES

[lunny]

I think this could be closed and we can track #28661.

[github-actions]

Automatically locked because of our CONTRIBUTING guidelines