August 2011 - cabal-devel

[Hackage] #767: Highlighted source code on hackage.haskell.org mangles Unicode
by Hackage 09 Nov '11

09 Nov '11

#767: Highlighted source code on hackage.haskell.org mangles Unicode ----------------------------------+----------------------------------------- Reporter: andersk | Owner: Type: defect | Status: new Priority: normal | Milestone: HackageDB Component: hackageDB website | Version: Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- On hackage.haskell.org, when you browse the source of a module that contains Unicode (e.g. [http://hackage.haskell.org/packages/archive/base- unicode-symbols/latest/doc/html/src/Data-Eq-Unicode.html Data.Eq.Unicode]), it is sent with a `Content-Type: text/html` header with no charset. There is a charset in the XML declaration `<?xml version="1.0" encoding="UTF-8"?>`, but that is ignored by Firefox because of the non-XML `Content-Type`. Therefore, the wrong encoding is detected and the Unicode symbols get mangled. Possible fixes include sending `Content-Type: text/html; charset=UTF-8`, or sending `Content-Type: application/xhtml+xml` so that the XML declaration is respected , or both (`Content-Type: application/xhtml+xml; charset=utf-8`), or adding equivalent `<meta http-equiv="Content-Type">` tags. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/767> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #821: Add support for Apache license
by Hackage 25 Oct '11

25 Oct '11

#821: Add support for Apache license ----------------------------+----------------------------------------------- Reporter: bos | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I have several projects licensed under the Apache license due to upstream dependencies, but Cabal doesn't know about it. This would be good to add for e.g. license compatibility checkers (I believe Galois has such a tool). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/821> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #857: Decide what to do about licenses
by Hackage 25 Oct '11

25 Oct '11

#857: Decide what to do about licenses ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: task | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Currently you can specify some partial info about a license in the .cabal file. It's not exhaustive and does not cover all licenses. It seems originally intended so that common licenses will be given the same name (so no confusion over "bsd" =? "BSD"). There are a number of outstanding requests for new licenses to be listed (#854 BSD2 & ISC, #821 Apache). This is based on users expecting that most licenses they might want should be listed. The current alternative of course is that they just list it as `OtherLicense`. So this all comes down to what do we want the license field for, what is it's purpose, does it have any semantics? Currently we can't really say that it has any reliable semantics (even if the info were accurate), it's really just a way to stop people spelling "GPL" wrong. It also serves a purpose to indicate what are recommended licenses, to work against license proliferation. So, should we move to a more accurate license system where you can express more precisely the licensing terms? Apart from listing more licenses this would mean we have to tackle: * multiple licenses (conjunctive): the distributor has to comply with multiple licenses, e.g. because different parts of the code have different licenses. * dual licensing (disjunctive): the distributor gets to pick which license to use * GPL open ended versions: The GPL recommends that authors license under terms like "Version X or any later version". This is a special kind of dual licensing, it's the infinite disjunction of all later versions of the license and of course those later versions are mostly unknown so it'd have to be handled specially. Then there's the issue in the BSD licenses that there's hardly any standard BSD3 license, people make up all kinds of variations. The 2-clause license is not actually (properly) listed by the FSF or the OSI (bizarrely the OSI has it listed but with the wrong text). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/857> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #876: Build fails for zlib 0.5
by Hackage 14 Sep '11

14 Sep '11

#876: Build fails for zlib 0.5 ----------------------------------+----------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Cabal library | Version: HEAD Severity: minor | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- Build fails when using zlib 0.5, version 0.5.3 works fine. Deps should be updated. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/876> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #879: source link broken for some Prelude types in online documentation
by Hackage 28 Aug '11

28 Aug '11

#879: source link broken for some Prelude types in online documentation --------------------------------+------------------------------------------- Reporter: mlinksva | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- http://hackage.haskell.org/packages/archive/base/latest/doc/html/Prelude.ht… links to http://hackage.haskell.org/packages/archive/base/latest/doc/ghc- prim-0.2.0.0/src/GHC-Types.html and http://hackage.haskell.org/packages/archive/base/latest/doc/integer- gmp-0.2.0.3/src/GHC-Integer-Type.html and http://hackage.haskell.org/packages/archive/base/latest/doc/ghc- prim-0.2.0.0/src/GHC-Bool.html which obtain 404s. Apologies if reporting bug in wrong place. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/879> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #299: Add changelog feature to hackagedb
by Hackage 18 Aug '11

18 Aug '11

#299: Add changelog feature to hackagedb --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: Platform: | --------------------------------+------------------------------------------- Comment(by dsfox): Replying to [comment:13 dsfox]: > Replying to [comment:10 ross]: > > I think that a changelog format that parsed to {{{[(Version, String)]}}} would be sufficient, though the {{{String}}} might require (Haddock-style?) markup. The additional info in Debian or Gentoo changelogs is available via the version number. > > Surely we also need to know when the entry was made and who made it? That is to say, we're talking about changelogs created upstream from any debian or gentoo packaging logs. We need to record authoritative information before that happens. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/299#comment:14> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

patch applied (cabal): "Drop assertion checking in the old solver"
by Duncan Coutts 18 Aug '11

18 Aug '11

Thu Aug 18 10:21:18 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Drop assertion checking in the old solver Make it a bit faster. M ./cabal-install/cabal-install.cabal -3 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Update version constraint on the Cabal library, for 1.12 release."
by Duncan Coutts 18 Aug '11

18 Aug '11

Thu Aug 18 10:19:55 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Update version constraint on the Cabal library, for 1.12 release. M ./cabal-install/cabal-install.cabal -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Add cabal sdist --zip flag for creating zip archives"
by Duncan Coutts 18 Aug '11

18 Aug '11

Thu Aug 18 10:17:21 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Add cabal sdist --zip flag for creating zip archives Handy if you want to send sources to people who do not grok .tar.gz Requires that the 'zip' program be installed (unlike for .tar.gz where we do it internally so that it works on all systems). M ./cabal-install/Distribution/Client/Setup.hs -2 +54 M ./cabal-install/Distribution/Client/SrcDist.hs -8 +50 M ./cabal-install/Main.hs -4 +4 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

Re: [Hackage] #299: Add changelog feature to hackagedb
by Hackage 17 Aug '11

17 Aug '11

#299: Add changelog feature to hackagedb --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: Platform: | --------------------------------+------------------------------------------- Comment(by dsfox): Replying to [comment:10 ross]: > I think that a changelog format that parsed to {{{[(Version, String)]}}} would be sufficient, though the {{{String}}} might require (Haddock- style?) markup. The additional info in Debian or Gentoo changelogs is available via the version number. Surely we also need to know when the entry was made and who made it? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/299#comment:13> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0