#227: Cabal-install does not track down build-tools: dependencies?
-+--
Reporter: guest |Owner:
Type: defect | Status: new
Priority: normal |M
On Thu, 2008-01-31 at 17:41 +, Ross Paterson wrote:
> On Thu, Jan 31, 2008 at 03:41:59PM +, Duncan Coutts wrote:
> > On Thu, 2008-01-31 at 14:37 +, Alistair Bayley wrote:
> > > On 31/01/2008, Duncan Coutts <[EMAIL PROTECTED]> wrote:
> > > OK. Ian voted for '.' as empty line, so I went
On Thu, Jan 31, 2008 at 03:41:59PM +, Duncan Coutts wrote:
> On Thu, 2008-01-31 at 14:37 +, Alistair Bayley wrote:
> > On 31/01/2008, Duncan Coutts <[EMAIL PROTECTED]> wrote:
> > OK. Ian voted for '.' as empty line, so I went with that as it was the
> > only comment, and was a positive one.
"Alistair Bayley" <[EMAIL PROTECTED]> writes:
> I have a feeling his preprocessor doesn't cover this case, from a
> brief inspection. He uses {- -} to delimit comment sections, rather
> than -- for comment lines.
Yes, that's right, it doesn't permit a non-haddock comment
to follow a haddock comme
Duncan Coutts <[EMAIL PROTECTED]> writes:
> On Thu, 2008-01-10 at 14:25 +, Alistair Bayley wrote:
>
>> the comment block (like cabal does)
>> - don't indent code relative to comments, because Haddock doesn't like this
>
> Hmm, we will have to find another solution to this because the H98 unli
Duncan Coutts <[EMAIL PROTECTED]> writes:
> On Thu, 2008-01-31 at 14:37 +, Alistair Bayley wrote:
>> As for a wider discussion, I'm all for it, but I believe the impact of
>> this change on existing code should be negligible (pending further
>> testing, of course), so I'm not sure if we're goi
> Ok, yes. So how about what I just implemented, that you put two blank
> lines between the named chunks?
Yes, that would work. You just need some way of separating/continuing
comment blocks, whatever it is.
> In particular I'd like to know how well it works for Jon Fairbairn who
> has .lhs code
On Thu, 2008-01-31 at 15:46 +, Alistair Bayley wrote:
> > To be honest, it's not clear to me that we need any distinction at all
> > since people can just swap the order of the comments:
> >
> > -- some more comments about x
> > --
> > -- | A description of x
> >
> > x = ...
>
> Yes, this is
#226: Cabal install should upgrade in the correct order.
-+--
Reporter: guest |Owner:
Type: enhancement | Status: new
Priority: normal |Milestone:
> To be honest, it's not clear to me that we need any distinction at all
> since people can just swap the order of the comments:
>
> -- some more comments about x
> --
> -- | A description of x
>
> x = ...
Yes, this is not a good motivating example, just an example. However,
a good motivating exam
On Thu, 2008-01-31 at 14:37 +, Alistair Bayley wrote:
> On 31/01/2008, Duncan Coutts <[EMAIL PROTECTED]> wrote:
> > I'm going to try and get this integrated. I'm not happy yet with the
> > issue about blank lines vs '.' lines etc etc. I think that needs a wider
> > discussion but I don't want
#226: Cabal install should upgrade in the correct order.
-+--
Reporter: guest |Owner:
Type: enhancement | Status: new
Priority: normal |Milestone:
On Thu, 2008-01-31 at 15:00 +, Ross Paterson wrote:
> On Sun, Jan 20, 2008 at 04:39:11PM -0800, Duncan Coutts wrote:
> > Thu Jan 17 14:36:10 PST 2008 Lennart Kolmodin <[EMAIL PROTECTED]>
> > * Implement QA for PackageDescription
> > Addresses #191 (QA) and #180 (QA for missing license).
>
#217: Main modules in .hsc files are not included in sdist
+---
Reporter: gwern |Owner:
Type: defect | Status: reopened
Priority: normal |Milestone: Cabal-1.
#225: allow installing just specific bits, like just docs
+---
Reporter: duncan |Owner:
Type: enhancement| Status: new
Priority: normal |Milestone:
Comp
#225: allow installing just specific bits, like just docs
+---
Reporter: duncan |Owner:
Type: enhancement| Status: new
Priority: normal |Milestone:
Comp
On Sun, Jan 20, 2008 at 04:39:11PM -0800, Duncan Coutts wrote:
> Thu Jan 17 14:36:10 PST 2008 Lennart Kolmodin <[EMAIL PROTECTED]>
> * Implement QA for PackageDescription
> Addresses #191 (QA) and #180 (QA for missing license).
> This patch only adds a new exposed module, it's not yet used a
On Sat, 2008-01-05 at 23:14 +, Alistair Bayley wrote:
> Another example:
>
> Let's say you want to produce this .hs output for Haddock:
>
> -- | A description of x
> --
> -- some more comments about x
>
> x = ...
>
>
> Now imagine you want to produce this .hs:
>
> -- | A description of
On Thu, 2008-01-10 at 14:25 +, Alistair Bayley wrote:
> the comment block (like cabal does)
> - don't indent code relative to comments, because Haddock doesn't like this
Hmm, we will have to find another solution to this because the H98 unlit
spec clearly states that '>' is to be replaced wi
Thu Jan 31 06:39:33 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Improve wording of -O and -O2 QA tests.
Including a typo noted by Johan Tibell.
M ./Distribution/PackageDescription/QA.hs -4 +4
___
cabal-devel mailing list
cabal-devel@haskell.or
On 31/01/2008, Duncan Coutts <[EMAIL PROTECTED]> wrote:
> I'm going to try and get this integrated. I'm not happy yet with the
> issue about blank lines vs '.' lines etc etc. I think that needs a wider
> discussion but I don't want to hold up what we already have.
OK. Ian voted for '.' as empty li
Thu Jan 31 06:29:01 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Adjust unlit's behaviour on continuing comments
This behaviour is not set in stone, there is not full agreement yet.
The previous code was deciding wether to continue a comment based on wether
the intervenienting lines were c
I can't easily send patches from work so I'll report this bug before I
forget about it. There's a typo in
Distribution/PackageDescription/QA.hs
ghcWarn "-O2" $
"-O2 is rarely needed as it often prolong the compile time "
++ "with usually with little benefit."
Notice the extra
Thu Jan 31 03:59:53 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Use Setup.hs like everyone else does
and note the issue about custom vs simple build-type for Cabal itself.
./Setup.lhs -> ./Setup.hs
M ./DefaultSetup.hs -1
M ./Makefile -1 +1
M ./Setup.hs -7 +9
___
Thu Jan 31 03:57:39 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Improve the QA messages a bit, use the same style as the sanity check
messages
Slightly more like full sentances and using '' quotes for field names etc.
M ./Distribution/PackageDescription.hs -1 +1
M ./Distribution/Pac
Thu Jan 31 03:49:09 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Find original sources for main-is when creating sdist
Also add a package sanity check that main-is must specify a .hs or .lhs file.
So the bahaviour is now that main-is specifies the main source file, even if
that is generate
Thu Jan 31 03:45:11 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Eliminate now-redundant Bool flag on smartCopySources
and simplfy the implementation to be a simple composition of
findFileWithExtension' and copyFiles with some additonal error checking.
M ./Distribution/Simple/GHC.hs -2
Thu Jan 31 03:41:43 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Stop using smartCopySources in SrcDist
This was the old module using it in with preserveDirs = True.
Anyway, we should be using smartCopySources for each lib and exe, we should be
collecting all the files to copy together int
Thu Jan 31 03:37:26 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* findPackageDesc has to return a relative path for SrcDist
otherwise we fail to copy the .cabal file when into the src tree
M ./Distribution/Simple/Utils.hs -1 +1
___
cabal-devel m
Wed Jan 30 03:28:42 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Remove one Bool parameter to smartCopySources which was True in all uses
The remaining Bool parameter is False for all uses except in SrcDirs
M ./Distribution/Simple/GHC.hs -2 +2
M ./Distribution/Simple/Hugs.hs -2 +2
Tue Jan 29 16:18:45 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Remove handling for .hi-boot files, which was only needed for ghc-6.2
which we have removed support for. It is not clear if we need any similar
handling for .hs-boot files. These were also the only uses of smartCopySources
wh
Tue Jan 29 16:08:48 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Remove utils testing code for functions that are being removed
M ./Distribution/Simple/Utils.hs -45
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailm
Tue Jan 29 16:01:29 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Simplify smartCopySources using findFileWithExtension' and copyFiles
Previously it used moduleToFilePath2 which returns all the locations in which
a source file is found, in different search dirs and with different extensions
Sat Dec 29 17:38:43 PST 2007 Duncan Coutts <[EMAIL PROTECTED]>
* Update testsuite for unlit changes
Follow the H98 report and replace ">" with " " not "".
Output the whitespace for blank lines rather than "".
Adjust to changes in unlit error handling, now more explicit.
M ./tests/Unli
Tue Jan 29 15:55:59 PST 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Add utils functions copyFiles, findFileWithExtension, findFileWithExtension'
and rewrite findFile in a similar style. These are to help simplify and
replace the existing functions smartCopySources, moduleToFilePath and
module
Sat Dec 29 17:37:23 PST 2007 Duncan Coutts <[EMAIL PROTECTED]>
* Add Alistair Bayley's unlit test suite
A ./tests/UnlitTest.hs
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel
Sat Dec 29 17:25:30 PST 2007 Duncan Coutts <[EMAIL PROTECTED]>
* Refactor unlit code to improve error and line pragma handling
And to make it more like the original code that classified lines
separately from checking and transforming them.
M ./Distribution/Simple/Hugs.hs -3 +7
M ./D
Tue Dec 4 13:13:56 PST 2007 [EMAIL PROTECTED]
* haddock: run unlit before cpp, like ghc does.
M ./Distribution/Simple/Haddock.hs -8 +12
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel
Tue Dec 4 13:15:50 PST 2007 [EMAIL PROTECTED]
* unlit preserves comments for Haddock's benefit. More complex algorithm to
handle cases where we want blank lines (containing whitespace) to become
comment lines in the output.
M ./Distribution/Simple/PreProcess/Unlit.hs -59 +73
___
Could someone file a feature request please with a sketch of a proposed
user interface.
Duncan
On Fri, 2008-01-04 at 16:49 +, Ian Lynagh wrote:
> On Sat, Dec 29, 2007 at 07:00:49PM +, Duncan Coutts wrote:
> >
> > On Mon, 2007-12-24 at 12:10 +, Ian Lynagh wrote:
> > >
> > > Related t
I'm going to try and get this integrated. I'm not happy yet with the
issue about blank lines vs '.' lines etc etc. I think that needs a wider
discussion but I don't want to hold up what we already have.
So I'll integrate it without the '.' line handling for now and we can
discuss it further as nec
#221: need a way to specify site-specific include and library search paths
+---
Reporter: guest |Owner:
Type: enhancement| Status: new
Priority: normal
On Wed, 2008-01-30 at 19:45 -0800, Peter Higley wrote:
> Thanks for adding the documentation. I was going to get to this and
> just didn't have time to get to it.
No problem. I'll let you look at the next bug fix or feature instead :-)
Duncan
___
cab
#224: allow specifying package version constraints to configure
+---
Reporter: duncan |Owner:
Type: enhancement| Status: new
Priority: normal |Milestone: Cab
44 matches
Mail list logo
