Re: [Hackage] #15: implement dependency analysis

: +--- Comment (by guest): See also: * #216 - specify more kinds of dependencies in .cabal files * #177 - check for required directories * # 262 - check for required foreign libraries -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/15#comment:5 Hackage http

Re: [Hackage] #216: need a way to specify the foreign libraries a package depends on

--+- Comment (by guest): #177 is actually about checking for directories. See also: * #15 and #159 - implement dependency analysis * #262 - check for required foreign libraries -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/216#comment:4

Re: [Hackage] #159: cabal dependencies

: +--- Comment (by guest): See also: * #216 - specify more kinds of dependencies in .cabal files * #177 - check for required directories * #262 - check for required foreign libraries -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/159#comment:2 Hackage http://haskell.org

[Hackage] #263: Multiple compilers of the same version confuse Cabal

/hackage/ticket/263 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #263: Multiple compilers of the same version confuse Cabal

(by guest): Sorry, of course that should be /usr/local/lib/foo-1.2.3.4/opt_local_ghc-6.8.2 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/263#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel

Re: [Hackage] #263: Multiple compilers of the same version confuse Cabal

-- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/263#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #262: Check for required C libraries during configure

. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/262#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #15: implement dependency analysis

to this ticket. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/15#comment:7 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal

Re: [Hackage] #216: need a way to specify the foreign libraries a package depends on

--+- Comment (by duncan): Module/file dependency analysis is not relevant (#15 and #159). That's a different kind of dependency. #177 and #262 are closely related though. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/216#comment:5 Hackage http

Re: [Hackage] #15: implement make-style module/file dependency framework

what kind of dependencies we're talking about. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/15#comment:8 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http

Re: [Hackage] #159: make-style module/file dependencies

for required foreign libraries Different kind of dependencies, those are inter-package dependencies. This ticket is about make-style module/file dependencies. I'm renaming the ticket to make that clear. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/159#comment:3 Hackage http

Re: [Hackage] #263: Multiple compilers of the same version confuse Cabal

hashes would be different, and if they were the same then their content would also be the same so it'd also be ok. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/263#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #166: sdist puts Happy-generated .hs files in the wrong place

is that tarballs that have pre-generated files in dist/ will get cleaned. They should really go in another dir that is checked but not cleaned. I'll open a separate bug on that issue. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/166#comment:2 Hackage http://haskell.org/cabal/ Hackage

Re: [Hackage] #233: case of Boolean values true and false should not matter

uploading packages to hackage that contain true and all the users of Cabal-1.2 will get very unhelpful parse errors. We've made a number of changes to the parser recently to make it handle unknown values better, but we've been pretty careful to not make it accept any new values so as not to cause

Re: [Hackage] #233: case of Boolean values true and false should not matter

: +--- Comment (by guest): The documentation uses all of True, true, False, and false, so it seems reasonable to accept them. After all, there is no suggestion anywhere in the docs that any other field values must follow Haskell literal syntax. -- Ticket URL: http://hackage.haskell.org/trac/hackage

Re: [Hackage] #233: case of Boolean values true and false should not matter

. That seems user friendly to me. We also wanted to prevent packages that differ only in case from being uploaded to hackage since we usually have to store package info in file systems and Windows and OS X use case insensitive file systems by default. Also, linux distros often like to lowercase

Re: [Hackage] #233: case of Boolean values true and false should not matter

(by duncan): * status: reopened = closed * resolution: = fixed Comment: Now a warning, for example: {{{ Warning: The 'default' field is case sensitive, use 'True' or 'False'. }}} So as long as hackage rejects packages with parse warnings this'll work ok. -- Ticket URL: http

Re: [Hackage] #145: Hackage does not support UTF-8 characters

#145: Hackage does not support UTF-8 characters +--- Reporter: guest |Owner: Type: defect | Status: new Priority: normal

Re: [Hackage] #145: Hackage does not support UTF-8 characters

#145: Hackage does not support UTF-8 characters +--- Reporter: guest |Owner: Type: defect | Status: new Priority: normal

Re: [Hackage] #223: allow per-package configuration options in config file

for two different commands. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/223#comment:5 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org

[Hackage] #267: cabal upload has poor error messages (just an HTTP response code)

the homeomorphic library I have written. To play along, you can do darcs get --partial http://www.cs.york.ac.uk/fp/darcs/homeomorphic $ cabal upload dist E:\Neil\homeomorphiccabal upload dist\homeomorphic-0.1.tar.gz Hackage username: NeilMitchell Hackage password: yoda Uploading dist\homeomorphic

[Hackage] #268: cabal upload asks for a password in plain text

command console. getChar in a loop? You can always do: c - getChar putChar '*' If you so feel like it. You can even use putStr \b \b to move back one character, even on Windows. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/268 Hackage http://haskell.org/cabal/ Hackage: Cabal

Re: [Hackage] #267: cabal upload has poor error messages (just an HTTP response code)

URL: http://hackage.haskell.org/trac/hackage/ticket/267#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

[Hackage] #270: Build executables that can be run in-place

directly, which would be useful for test suites, for example. David -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/270 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org

Re: [Hackage] #184: cabal-install should report build results to hackage server

#184: cabal-install should report build results to hackage server -+-- Reporter: duncan |Owner: Type: enhancement | Status: closed Priority: high

Re: [Hackage] #268: cabal upload asks for a password in plain text

: +--- Changes (by duncan): * difficulty: normal = very easy (1 hour) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/268#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #264: unionBuildInfo should not always use nub

: +--- Changes (by duncan): * difficulty: normal = easy (4 hours) * milestone: = Cabal-1.4 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/264#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #253: Check for invalid operating system names

it into Cabal-1.4. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/253#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman

Re: [Hackage] #171: Add command to automagically create an initial cabal package

-+-- Changes (by duncan): * milestone: = Cabal-2.0 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/171#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel

Re: [Hackage] #265: Cabal field stability not useful

should just deprecate it and add a field for the api versioning scheme, like the package versioning policy. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/265#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #264: unionBuildInfo should not always use nub

: +--- Changes (by duncan): * status: new = closed * resolution: = fixed Comment: So we now do not use nub on all the options fields, and the `x-*` extension fields. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/264#comment:2 Hackage http

Re: [Hackage] #224: allow specifying package version constraints to configure

(it is just silently ignored.) }}} -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/224#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http

Re: [Hackage] #253: Check for invalid operating system names

/hackage/ticket/253#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #253: Check for invalid operating system names

: +--- Changes (by duncan): * status: new = closed * resolution: = fixed -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/253#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___

Re: [Hackage] #232: implement extended syntax for package version ranges

: +--- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/232#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http

Re: [Hackage] #225: allow installing just specific bits, like just docs

: +--- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/225#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http

Re: [Hackage] #218: Data-files have no way of being installed conditionally

+--- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/218#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org

Re: [Hackage] #177: Check Include-dirs, extra-lib-dirs etc exist at configure time.

+--- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/177#comment:9 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___

Re: [Hackage] #137: setup sdist places implementation-dependent preprocessor output in the source bundle

--+- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/137#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #91: Building executables that use Template Haskell for profiling

+--- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/91#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal

Re: [Hackage] #216: need a way to specify the foreign libraries a package depends on

--+- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/216#comment:6 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___

Re: [Hackage] #266: cabal haddock plus cpp preprocessing with relative #include files

: +--- Changes (by duncan): * milestone: = Cabal-1.6 -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/266#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel

Re: [Hackage] #271: The index page should link to a package, not a package version

: +--- Changes (by ross): * type: defect = enhancement Comment: That might help a little. Presumably the recent additions list (and RSS feed) should still point at specific versions. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/271#comment:1 Hackage http

[Hackage] #272: Support 'cabal help' in addition to 'cabal --help'

(who are likely to type help!) and experienced users as well (same syntax for all your tools). The first, and probably easiest thing would be to just support 'cabal help' but I would be nice with 'cabal help command' as well. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/272

Re: [Hackage] #225: allow installing just specific bits, like just docs

URL: http://hackage.haskell.org/trac/hackage/ticket/225#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #272: Support 'cabal help' in addition to 'cabal --help'

--help Should still work with command line completion. }}} -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/272#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel

Re: [Hackage] #265: Cabal field stability not useful

entirely follow; since it's not being used much, or for any particular purpose, deprecation isn't a bad idea. But I'm not exactly sure what you mean by 'a field for the api versioning scheme'. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/265#comment:2 Hackage http://haskell.org

Re: [Hackage] #232: implement extended syntax for package version ranges

: +--- Comment (by duncan): Note that if the `foo ~ 1.2.1+` syntax is too confusing we could do with just `foo ~ 1.2.* = 1.2.1`. It also allows to depend on a micro release that fixes a bug like `foo ~ 1.2.* = 1.2.0.1`. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/232#comment:2

[Hackage] #275: On each package page, give the name of the corresponding debian package

| +--- This is a feature request. I don't know enough to know if this is a good idea, maybe there's a better way of tracking down which debian package to get for a given hackage package. Maybe you could also give corresponding package names for other operating systems. All I know

Re: [Hackage] #276: Add support for convenience libraries

: +--- Changes (by duncan): * difficulty: normal = project( week) Comment: There is the constraint that there be at most one installable library so I'm not sure a bool flag is quite right. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/276#comment:1

Re: [Hackage] #275: On each package page, give the name of the corresponding debian package

to the Debian-Haskell mailing list if you can't find one). The main problem with putting it on particular packages' pages is that we'd have to know whether Debian (or, in general, any OS) actually has a package for it. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/275#comment:2 Hackage

Re: [Hackage] #271: The index page should link to a package, not a package version

: +--- Changes (by ross): * status: new = closed * resolution: = fixed -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/271#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal

Re: [Hackage] #278: Default to non-versioned links in Hackage index

#278: Default to non-versioned links in Hackage index +--- Reporter: guest |Owner: Type: enhancement| Status: closed Priority: low|Milestone

Re: [Hackage] #278: Default to non-versioned links in Hackage index

#278: Default to non-versioned links in Hackage index +--- Reporter: guest |Owner: Type: enhancement| Status: closed Priority: low|Milestone

Re: [Hackage] #260: cabal upgrade runs install on the current package instead of upgrading installed packages

It shares most code anyway. Also fixes ticket #260 becuase we use the right entry point now. }}} -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/260#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___

[Hackage] #279: Cabal-upload could have a smarter default

-- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/279 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #244: Add Changelog summary feature to sdist

worth noting that I learned today there's an even better way: 'darcs changes --from-tag=.'. -- gwern -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/244#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___

Re: [Hackage] #244: Add Changelog summary feature to sdist

couldn't be bothered for Monotone, Codeville, or Bazaar.) You can find it here: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/change- monger-0.0 I hope y'all will consider incorporating the code into Cabal, or at least maybe adding some sort of option. -- gwern -- Ticket URL

Re: [Hackage] #244: Add Changelog summary feature to sdist

of whether it's mentioned in the cabal file or anything. So you could at least do something like: function sdist () { change-monger; cabal sdist --include=ChangeLog; } -- gwern -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/244#comment:5 Hackage http://haskell.org/cabal/ Hackage

Re: [Hackage] #280: Cabal doesn't work with hs-boot and preprocessed sources.

(by guest): * reporter: guest = kr.angelov -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/280#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http

[Hackage] #280: Cabal doesn't work with hs-boot and preprocessed sources.

/hackage/ticket/280 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #214: Package security

: +--- Comment (by ross): I don't appreciate having my time wasted with demonstrations of the bleedin' obvious. I'll delete the username of the next demonstrator. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/214#comment:5 Hackage http://haskell.org/cabal/ Hackage: Cabal

Re: [Hackage] #214: Package security

. As for users downloading bad packages, perhaps we should ask why they might be more likely to download and run an unknown package from hackage than say `132.73.41.22/hax0r.sh`. We should be careful not to give any false sense of security. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/214

Re: [Hackage] #214: Package security

: +--- Comment (by guest): I agree with int-e - by putting something on hackage, and telling everyone that hackage is great, we are putting some faith in the system. I think instead of trusting packages, we should be trusting uploaders. There aren't going to be many people who write 3 real

Re: [Hackage] #214: Package security

://hackage.haskell.org/trac/hackage/ticket/214#comment:9 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #214: Package security

rating. And those five could be 500 if it's suitably advertised, an oft requested feature or a popular idea. Try adding a package to Hackage that claims it adds a dependently typed system to Haskell and watch the number of downloads! And if such a package as that is trojaned... -- matthew

Re: [Hackage] #214: Package security

. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/214#comment:11 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #214: Package security

) They also have co-maintainers for packages, and they require admin intervention for taking over orphaned packages. (http://www.nntp.perl.org/group/perl.cvs.perlfaq/2007/07/msg393.html) - int-e -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/214#comment:12 Hackage http://haskell.org/cabal

Re: [Hackage] #214: Package security

://hackage.haskell.org/trac/hackage/ticket/214#comment:13 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #214: Package security

: +--- Comment (by duncan): Replying to [comment:10 guest]: I worry about the idea of providing security or some notion of safety or trust only if one behaves as expected. That seems slightly odd to me. I think it's really essential. You are expecting for some reason that something on hackage

Re: [Hackage] #214: Package security

for some reason that something on hackage is held to a higher security or QA standard than something else you randomly download off the web. What gives you that confidence? What makes you think other users have that confidence? Perhaps that's the security problem. There's no security problem

Re: [Hackage] #226: Cabal install should upgrade in the correct order.

/trac/hackage/ticket/226#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #174: cabal-install tries to upgrade the base package

that are not upgradable. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/174#comment:6 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal

Re: [Hackage] #174: cabal-install tries to upgrade the base package

-+-- Changes (by duncan): * status: new = closed * resolution: = fixed Comment: {{{ Wed May 21 16:37:00 BST 2008 Duncan Coutts [EMAIL PROTECTED] * Hide any available base and ghc-prim packages from the dep resolver Previously if the base package was available on hackage

Re: [Hackage] #277: add data-dir field

in the data-dir field, allowing package authors to better structure their source tree. There's no behavioural change by default. Fri May 9 14:13:06 BST 2008 Bertram Felgenhauer [EMAIL PROTECTED] * document data-dir field }}} -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket

Re: [Hackage] #270: Build executables that can be run in-place

for package Foo, you'd use Foo_bindir=... Foo_datadir=... Foo_libexecdir=... ./Foo The next step would be generating a wrapper script that allows running the program inplace. It should also work for a library. }}} -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/270#comment:2

Re: [Hackage] #261: Marking packages deprecated

: +--- Changes (by guest): * cc: [EMAIL PROTECTED] (added) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/261#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal

Re: [Hackage] #261: Marking packages deprecated

: +--- Comment (by guest): The Safe package has been superseded by the safe package, and it would be nice to indicate the explicit upgrade path. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/261#comment:3 Hackage http://haskell.org/cabal

Re: [Hackage] #175: cabal-install needs a new package dependency resolution algorithm

-+-- Changes (by guest): * cc: [EMAIL PROTECTED] (added) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/175#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel

[Hackage] #282: profiling versions of libraries not managed well

for the normal build? When do we just give up and make the user figure it out? -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel

Re: [Hackage] #234: track installed files to allow uninstall

: +--- Changes (by guest): * cc: Misha, Aizatulin, [EMAIL PROTECTED] (added) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/234#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel

[Hackage] #283: install command doesn't install dist/doc/users-guide/

the contents of dist/doc/html are copied to their install location. The users guide doesn't get installed. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/283 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel

Re: [Hackage] #283: install command doesn't install dist/doc/users-guide/

| Platform: --+- Changes (by guest): * cc: Misha, Aizatulin, [EMAIL PROTECTED] (removed) * reporter: guest = Misha Aizatulin [EMAIL PROTECTED] -- Ticket URL: http://hackage.haskell.org/trac/hackage

Re: [Hackage] #196: ability to specify custom args to haddock

): * cc: [EMAIL PROTECTED] (added) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/196#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org

Re: [Hackage] #283: install command doesn't install dist/doc/users-guide/

something? -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/283#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

[Hackage] #284: Cannot upload packages that require specific cabal versions

a package that requires a custom Setup.lhs.The package works for ghc 6.8.x and 6.6.x and, thus, the Setup.lhs script was designed to work with Cabal 1.2.x, the one that comes with ghc 6.8.x. This is clearly indicated in the cabal-version field. However, if I try to upload this package to hackage I

[Hackage] #285: hackage trac should permit registration

#285: hackage trac should permit registration +--- Reporter: guest |Owner: Type: enhancement| Status: new Priority: normal |Milestone: Component

[Hackage] #286: have alphabetical sorted package list as well as categorized one

: | +--- the hackage package list ought to have a link to an alphabetically sorted variant (i often know the package name, but not the likely categories, so i tend to 'search' on that page..). even after hoogle for search, it'd be nice (and probably easy to arrange) to be able to browse both by category

[Hackage] #287: make better use of existing build/failure reports (provide stats, alert authors)

: | +--- the hackage package list ought to list successful and failed builds (simply a list of compiler versions, each one green or red, depending on success, with direct link to build/failure log; this would fit into the one-line-per-package format) for each entry, and report them

[Hackage] #288: the package indexes are very slow

trying to make a plan to install 560 packages from hackage: {{{ $ cabal install --dry-run $(cat pkgs) }}} it turns out (according to the ghc profile), 91% of the time is spent reading the index of installed and available packages. The ghc package index is a couple of massive text files

Re: [Hackage] #288: the package indexes are very slow

://hackage.haskell.org/trac/hackage/ticket/288#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #131: cabal-install should rebuild dependants when a package is upgraded

C against A-1.0 or to rebuild B-1.0 to use A-2.0. So it's less clear that we need this feature. That's not to say it's never needed, just that it's not the common case any more. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/131#comment:4 Hackage http://haskell.org/cabal

Re: [Hackage] #198: outline for revamp of cabal install and upgrade behavior

available version rather than the installed versions. This is the maximal upgrade. {{{ $ cabal upgrade }}} means upgrade for all the packages currently installed. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/198#comment:7 Hackage http://haskell.org/cabal/ Hackage: Cabal

[Hackage] #289: symlink binaries into ~/bin

: $HOME/.cabal/bin symlink-bindir: $HOME/bin }}} -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/289 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http

[Hackage] #290: Cabal does some work behind the back of hooks

}}} The reason I want to do this is so that `Setup.hs` can take care of building itself in multiple ways, using different dist directories. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/290 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #290: Cabal does some work behind the back of hooks

it externally? That is have the external script build the package multiple times with different dist dirs and config options? -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/290#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #290: Cabal does some work behind the back of hooks

://hackage.haskell.org/trac/hackage/ticket/290#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #265: Cabal field stability not useful

: normal = low * severity: normal = minor * milestone: = _|_ -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/265#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel

Re: [Hackage] #262: Check for required C libraries during configure

: +--- Changes (by duncan): * priority: normal = high * difficulty: normal = easy (4 hours) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/262#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

Re: [Hackage] #250: 'haddock --executables should dump the haddock interface too

+--- Changes (by duncan): * status: new = closed * resolution: = fixed Comment: Applied. Well, actually I had to change it a bit because of more recent changes. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/250#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related

<    1   2   3   4   5   6   7   8   9   10   >