patch applied (cabal): fix help text (--PROG-arg is now --PROG-option)

Thu Oct 25 17:10:45 PDT 2007 Ross Paterson <[EMAIL PROTECTED]> * fix help text (--PROG-arg is now --PROG-option) M ./Distribution/Simple/Setup.hs -1 +1 ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/c

Re: presentation of dependencies in the web interface

On Thu, Oct 25, 2007 at 02:02:22PM +0200, Thomas Schilling wrote: > The point is, that flags like "old-base" or "bytestring-in-base" (as, > for example, in [1]) are used solely to dispatch on the version of the > base package. It should not be necessary for the user to invent flag > names for such

Re: presentation of dependencies in the web interface

On Thu, 2007-10-25 at 11:40 +0100, Ross Paterson wrote: > Dependencies between packages are obviously more complex now that we > have configurations. > > The web interface now has an experimental presentation of these > dependencies transformed into disjunctive normal form, with the atoms > being

Re: [Hackage] #87: robustify & release cabal-get

#87: robustify & release cabal-get +--- Reporter: paolo |Owner: paolo Type: task | Status: closed Priority: normal |Milestone: Component: cabal-install |

Re: presentation of dependencies in the web interface

On Thu, 2007-10-25 at 12:48 +0100, Ross Paterson wrote: > On Thu, Oct 25, 2007 at 01:17:43PM +0200, Thomas Schilling wrote: > > I presume the final interface should be to give the user a simple way to > > query the dependenies by giving assignments for OS, arch, > > implementation, etc. and then dy

Re: [Hackage] #54: if a package is already newest version, avoid downloading and installing it

#54: if a package is already newest version, avoid downloading and installing it +--- Reporter: ijones |Owner: ijones Type: defect | Status: closed Priority: normal |

Re: [Hackage] #29: perform package dependency analysis for cabal-install

#29: perform package dependency analysis for cabal-install +--- Reporter: ijones |Owner: ijones Type: enhancement| Status: closed Priority: normal |Milestone: Cabal-1.

Re: [Hackage] #130: cabal-install ignores version numbers when parsing package identifiers

#130: cabal-install ignores version numbers when parsing package identifiers +--- Reporter: mnislaih |Owner: mnislaih Type: defect | Status: closed Priority: no

Re: [Hackage] #129: fetch fails without giving user feedback if the requested package does not exist

#129: fetch fails without giving user feedback if the requested package does not exist +--- Reporter: mnislaih |Owner: mnislaih Type: defect | Status: closed Pri

Re: presentation of dependencies in the web interface

On Thu, Oct 25, 2007 at 01:17:43PM +0200, Thomas Schilling wrote: > I presume the final interface should be to give the user a simple way to > query the dependenies by giving assignments for OS, arch, > implementation, etc. and then dynamically (yes, using JavaScript) > updating the dependency list

Re: [Hackage] #87: robustify & release cabal-get

#87: robustify & release cabal-get +--- Reporter: paolo |Owner: paolo Type: task | Status: new Priority: normal |Milestone: Component: cabal-install |

Re: [Hackage] #61: cabal-install should detect installed packages, as does cabal-get

#61: cabal-install should detect installed packages, as does cabal-get +--- Reporter: anonymous |Owner: ijones Type: enhancement| Status: closed Priority: normal |Milestone:

Re: [Hackage] #35: cabal-get needs a way to list available packages

#35: cabal-get needs a way to list available packages -+-- Reporter: [EMAIL PROTECTED] |Owner: ijones Type: enhancement | Status: closed Priority: normal |Milestone:

Re: presentation of dependencies in the web interface

On Thu, 2007-10-25 at 11:40 +0100, Ross Paterson wrote: > Dependencies between packages are obviously more complex now that we > have configurations. > > The web interface now has an experimental presentation of these > dependencies transformed into disjunctive normal form, with the atoms > being

presentation of dependencies in the web interface

Dependencies between packages are obviously more complex now that we have configurations. The web interface now has an experimental presentation of these dependencies transformed into disjunctive normal form, with the atoms being simple version ranges. It lacks tests of os, arch and impl, which w