If yes, then try to build it from its source. Then it can be published in main
Why are you putting the package in non-free ?
What license did you put your software under ?
There's rule regarding GPL software and packaging that must be followed...
I'd also suggest that you publish your package somewhere on a public server.
I'm continuing to look around at things - do all packages, even those in non-free, have to have an accompanying .dsc file to be in the Debian repositories?
<mailto:mechtilde@debian.org>
If yes, then try to build it from its source. Then it can be
published in main
<mailto:debian@polynamaude.com>
Why are you putting the package in non-free ?
What license did you put your software under ?
makedeb is licensed under the GPL3 license.
The goal was to be able to just distribute the binary form of the
packages, as that's all that I get/use when I build it myself (the
helper application, makepkg, handles all the source files, and the
rest is just built into a binary package with makedeb itself).
<mailto:debian@polynamaude.com>
There's rule regarding GPL software and packaging that must be
followed...
I was looking at the following in the Debian Policy, which was
leading me to believe it would be fine:
"The non-free archive area contains supplemental packages intended to
work with the Debian distribution that do not comply with the DFSG or
have other problems that make their distribution problematic."
In this case the problems would be lack of a source package. Is there someplace else that says GPL programs have to be distributed under
source packages?
If you want to get makedeb into Debian, then you'll need to build a Debian source package for it.
If on the other hand you want to get the packages created by makedeb into Debian, you're probably out of luck.
The complete build system is based on a .dsc file and this does more than only run a gcc build on your application or package it into a .tar.gz file !
Hi,
On 2021-05-21 7:30 a.m., Hunter Wittenborn wrote:
If you want to get makedeb into Debian, then you'll need to
build a Debian source package for it.
If on the other hand you want to get the packages created bymakedeb into Debian, you're probably out of luck.
The only build system in Debian is Debian's build system based on
.dsc source file.
I'm continuing to look around at things - do all packages, even those in non-free, have to have an accompanying .dsc file to be in the Debian repositories?
> If you want to get makedeb into Debian, then you'll need to build
a Debian source package for it.
> If on the other hand you want to get the packages created by
makedeb into Debian, you're probably out of luck.
The complete build system is based on a .dsc file and this does morethan only run a gcc build on your application or package it into a
.tar.gz file !
That and the links all make sense, I'll see what I can do.
Thanks,
I'm asking myself how many package are only available in Arch and not in Debian.
notI'm asking myself how many package are only available in Arch and
in Debian.
Support for Arch Linux packages on Debian was a byproduct of makedeb,
but the main goal is to just provide an alternative to the Debian source package format.
On the topic of Arch Linux though, makedeb (and more specifically a side project for it) gives support for the AUR, which has /quite/ a few
packages not available in the Debian repos (most notably those with
license issues).
I also use it to get some up-to-date packages from the Arch repositories
on my Ubuntu system, which helps to avoid a ton of extra repositories
and PPAs.
Regardless of all that though, I think I got what I need to be able to
start somewhere.
Again, thanks for the help.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (3 / 13) |
Uptime: | 92:17:44 |
Calls: | 6,498 |
Calls today: | 9 |
Files: | 12,100 |
Messages: | 5,277,850 |