tandem/camper
tandem
/
camper
2
0
Fork 0
Code Issues 7 Pull Requests Packages Projects Releases Wiki Activity
camper/debian/copyright

57 lines
2.3 KiB
Plaintext
Raw Normal View History

Add Debian package Although it is way too soon to install the application on any server, i use build.opensuse.org as a kind of CI/CD server: it runs the migration and executes the test suite on each commit. For that, i need to build *some* package, and Debian suits be better because it has all the Go packages i use; i would have to create the RPM for many libraries if i were to use openSUSE, for instance. According to the de facto project layout for Go[0], these files should go into a `build/package` folder, but since i already broke the rules with Sqitch’s folders, i do not see why i have to go against Debian’s conventions of placing them into a `debian` subfolder of the root. I have spit the package into the binary and the Sqitch migration files because it is possible to want the PostgreSQL into a separate server, and there is little point of having Sqitch and all its dependencies installed on the front-end server where the Go program runs. The demo package is probably harder to justify, as it is just a single file, however i will not run out of packages, will i? Lintian detects htmx@1.9.3.min.js as a “source-less” file, which is practically true as nobody is ever going to edit a minified source. I did not want to include the source in the distribution package, that’s why i included it in the “missing sources” file, even thought this is a native debian package and, thus, can not have missing sources. git-buildpackage creates a lot of extra files that have to be removed to build it again, otherwise the process detects the new files in the directory and refuses to build the tarball. I was getting tired of doing it manually and added a Makefile rule. Closes #20
2023-07-27 17:20:29 +00:00
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Source: https://dev.tandem.ws/tandem/camper
Upstream-Name: camper
Upstream-Contact: jordi@tandem.blog
Files:
*
Copyright:
2023 jordi fita mas
Added copyright statement to files modified by Oriol
2024-01-16 16:58:49 +00:00
2024 Oriol Carbonell
Add Debian package Although it is way too soon to install the application on any server, i use build.opensuse.org as a kind of CI/CD server: it runs the migration and executes the test suite on each commit. For that, i need to build *some* package, and Debian suits be better because it has all the Go packages i use; i would have to create the RPM for many libraries if i were to use openSUSE, for instance. According to the de facto project layout for Go[0], these files should go into a `build/package` folder, but since i already broke the rules with Sqitch’s folders, i do not see why i have to go against Debian’s conventions of placing them into a `debian` subfolder of the root. I have spit the package into the binary and the Sqitch migration files because it is possible to want the PostgreSQL into a separate server, and there is little point of having Sqitch and all its dependencies installed on the front-end server where the Go program runs. The demo package is probably harder to justify, as it is just a single file, however i will not run out of packages, will i? Lintian detects htmx@1.9.3.min.js as a “source-less” file, which is practically true as nobody is ever going to edit a minified source. I did not want to include the source in the distribution package, that’s why i included it in the “missing sources” file, even thought this is a native debian package and, thus, can not have missing sources. git-buildpackage creates a lot of extra files that have to be removed to build it again, otherwise the process detects the new files in the directory and refuses to build the tarball. I was getting tired of doing it manually and added a Makefile rule. Closes #20
2023-07-27 17:20:29 +00:00
License: AGPL-3.0-only
Files:
web/static/htmx@1.9.3.min.js
Copyright:
2020 Big Sky Software
License: BSD-2-Clause
License: AGPL-3.0-only
Camper is free software: you can redistribute it and/or modify it under the
terms of the GNU Affero General Public License as published by the Free
Software Foundation, version 3.
.
Camper is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
.
You should have received a copy of the GNU Affero General Public License along
with CAmper. If not, see <https://www.gnu.org/licenses/>.
.
On Debian systems, the complete text of the GNU Affero General Public License
can be found in `/usr/share/common-licenses/AGPL-3'.
License: BSD-2-clause
All rights reserved.
.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
.
* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.