Comments (15)
This is probably the most important feature request, as copyright handling is most tedious.
I started working on this, but it does not play well --compare
, you should have a look. Maybe the copyright-related Atoms
need to be reconsidered and made more abstract, and maybe an existing machine-readable debian/copyright
needs to be parsed? You’ll know better what to do here.
Thanks!
from cabal-debian.
Where does the data in that template show up? I don't recognize those fields.
from cabal-debian.
That is an example debian/copyright
field, according to http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ – is that what you are asking?
from cabal-debian.
Yes, thanks.
from cabal-debian.
Free form copyright files are still legit, right?
from cabal-debian.
Closed by patch a5f512c. The type for the copyright field is now Maybe (Either CopyrightDescription Text). There is code to parse a CopyrightDescription, and to format a CopyrightDescription that is added to the atoms via the copyright lens. I will add an example to the test cases to show how to build a CopyrightDescription.
from cabal-debian.
There are actually some more changes coming to make this work properly.
from cabal-debian.
This is not working fully yet, is it? So to avoid confusion, I’ll reopen this.
from cabal-debian.
I just noticed that the copyright file for both the debian and cabal-debian package say "all rights reserved" - what is the appropriate license for these packages if Debian is going to use them? The license text looks MIT-ish I guess.
from cabal-debian.
Joachim, could you look at the License type in src/Debian/Policy.hs and consider how to implement conversions to and from the Cabal License type, how to pretty print for the License: field of debian/copyright, and how to parse that license field back into a Debian.Policy.License value? The package is "working", but I'm pretty sure its making a mess of the license fields in my packages.
from cabal-debian.
The current version lacks the stanza
Files: debian/*
Copyright: held by the contributors mentioned in debian/changelog
License: license-name
as described in the original post.
Also, empty lines in the license are not properly escaped (using a single .
).
from cabal-debian.
Joachim, could you look at the License type in src/Debian/Policy.hs and consider how to implement conversions to and from the Cabal License type
I’m reluctant to invest into this when it is not quite clear to me why we need this both ways. When exactly would I want to convert data from debian/copyright
to something understandable by Cabal
?
Also, the data type in Debian.Debianize.Types.CopyrightDescription
doesn’t quite cut it. Consider the example in the first post: The first line of the License
field contains the license name (which could be made-up and only used to reference within the file, hence foo license
), while the remaining lines are the actual license text. Your code currently puts it into a Comment
field.
Again, I feel sorry for not submitting a patch, but I’m still don’t see through the design of the code...
from cabal-debian.
This should be closed by 9b08957.
from cabal-debian.
But I'd better verify...
from cabal-debian.
Ok, this is ready for testing.
from cabal-debian.
Related Issues (20)
- Multi-Arch field not supported
- Test suite failure from Stackage HOT 5
- Needs a cross referencing between command line options and lens names
- can't detect gtk2hs-buildtools because it is looking for gtk2hsC2hs.pc HOT 4
- Generated versioned dependencies on libraries provided by GHC HOT 9
- src/Debian/Debianize/Goodies.hs:165:22: No instance for (Show (D.Server -> Int)) HOT 1
- Compile failure with GHC 7.8/7.6 HOT 7
- cabal-debian does not detect pkg-config HOT 2
- cabal-debian "confuses" library name and apt dependency HOT 2
- support build-profile notation for test-only build dependencies
- Add support for cabal custom-setup
- runInteractiveProcess: exec: does not exist HOT 2
- Prelude.read: no parse HOT 7
- build-depends for executables not handled correctly HOT 2
- release 4.38.2 to hackage HOT 5
- spurious linking against libffi and libatomic1 HOT 3
- cabal-debian fails for custom location of the ghc HOT 4
- cabal-debian 5.0.2 build failure HOT 1
- stackage: `verify-package cabal-debian` complains about tabs and misnamed cabal package
- Simple example for creating a Debian package HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cabal-debian.