Please declare a LICENSE

[DanielG]

Hi Nick,

I'd like to package ipv6utils for Debian, but the repo doesn't mention any license so it cannot be included as-is.

Could you decide on a license and declare it?

Easiest would be to just add a SPDX header in ipv6utils.go along with Copyright statement:

// SPDX-License-Identifier: MIT
// Copyright (C) <Your name and/or E-Mail>

See https://writefreesoftware.org/learn/participate/choose-a-license/ on how to choose and https://spdx.org/licenses/ for full the identifier list)

You can also go the extra mile and include a LICENSE file if you like, but it's not necessary for my purposes.

Thanks,
--Daniel <3

PS: I also notice the repo includes a compiled version of ipv6utils, I'd have to remove it when packaging -- which is a hassle ;-). You may want to consider using release assets for binaries instead of including them with the source code: https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository

[buraglio]

Done.

…

On Mon, Oct 27, 2025 at 6:02 AM Daniel Gröber (dxld) < ***@***.***> wrote: *DanielG* created an issue (buraglio/ipv6utils#9) <#9> Hi Nick, I'd like to package ipv6utils for Debian, but the repo doesn't mention any license so it cannot be included as-is. Could you decide on a license and declare it? Easiest would be to just add a SPDX header in ipv6utils.go along with Copyright statement: // SPDX-License-Identifier: MIT // Copyright (C) <Your name and/or E-Mail> See https://writefreesoftware.org/learn/participate/choose-a-license/ on how to choose and https://spdx.org/licenses/ for full the identifier list) You can also go the extra mile and include a LICENSE file if you like, but it's not necessary for my purposes. Thanks, --Daniel <3 PS: I also notice the repo includes a compiled version of ipv6utils, I'd have to remove it when packaging -- which is a hassle ;-). You may want to consider using release assets for binaries instead of including them with the source code: https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository — Reply to this email directly, view it on GitHub <#9>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHZT6W3NIR5OXYKCZSPYOT3ZXUU5AVCNFSM6AAAAACKJ6KBZKVHI2DSMVQWIX3LMV43ASLTON2WKOZTGU2TMMRSG43DOOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>