enumerations like `build-type`,
`tested-with`, `license` and `extensions` though it's not so clear in
those cases if it should be case sensitive or not.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/233#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
* resolution: = fixed
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/107#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
://hackage.haskell.org/trac/hackage/ticket/218#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
:
+---
Comment (by duncan):
The project description is haddock markup so adding links is already
possible. Perhaps that'd be enough if it was well known.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/237#comment:1
messages.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/216#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
to somehow inspect the content at the other end of the url to
guess what kind of repo it is.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/58#comment:6
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing
are a short description
of the respective package, to be used in overview pages.
If people adds lots and lots of links to the description field, the layout
of the package site on Hackage might also be less functional since some
information would move down.
--
Ticket URL: http://hackage.haskell.org
)
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/210#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
not sure what's the
best way to provide that. The hackageDB password file is in the same
Apache format used by Trac, so that could be a possibility. See also #57.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/237#comment:5
Hackage http://haskell.org/cabal/
Hackage: Cabal
/trac/hackage/ticket/237#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-devel
:
+---
Comment (by [EMAIL PROTECTED]):
The package list uses the Synopsis field (plain text), rather than
Description (haddock markup).
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/237#comment:3
Hackage http
on top, and authors are free to add more information into the
Description part. (At the same time we'd make the text column narrower,
which is good, too.)
Are you referring to the package list or the page for an individual
package?
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket
__HADDOCK__ a numeric value, because
GHC extensions need not be hidden from the new one.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/238
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal
-0.x.
We should be passing the cpp-options of course.
IMHO, we should still make Cabal do the pre-processing rather than have
ghc do it, but that's part of a larger task.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/238#comment:1
Hackage http://haskell.org/cabal/
Hackage
whether to trust a package is a social and
community issue, but the lack of transparency in discovering relevant
information is a technical problem that does have a solution.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239
Hackage http://haskell.org/cabal/
Hackage: Cabal
:
+---
Comment (by [EMAIL PROTECTED]):
It used to reject repeat uploads, but people complained. It can easily be
turned on again.
Putting the uploader and upload date on the package page is also in the
works.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239#comment:1
Hackage http
/obsolete/broken versions in the web UI.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org
with the same
version, so please don't apply the rejecting patch. But I do want to stop
anyone but me uploading packages for anything that I'm the maintainer of!
-- Neil Mitchell
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239#comment:3
Hackage http://haskell.org/cabal/
Hackage
that
it has to be overridable for the cases when a package maintainer
disappears.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239#comment:4
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
:
+---
Comment (by guest):
Yes, let it be overridden by a trusted admin type person. And let me say
who I think can upload my package. But I shouldn't be allowed to upload a
package on behalf of someone else without them knowing.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239#comment
need to weigh what security would actually be achieved by a particular
setup against the costs.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239#comment:6
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel
,
presumably because on MacOS X cp also copies the magic over.
Sorry for being so vague. Let me know if I can help in any way. -- Eric
Kow
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/240
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
for the makefile
to figure out where those links should point. (e.g. the wxcore package.)
The Make build-type ought to put these options in a HADDOCKOPTS setting on
the make command line, so that the makefile can pass these to haddock.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket
for the makefile
to figure out where those links should point. (e.g. the wxcore package.)
The Make build-type ought to put these options in a HADDOCKOPTS setting on
the make command line, so that the makefile can pass these to haddock.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket
:
--+-
Changes (by [EMAIL PROTECTED]):
* status: new = closed
* resolution: = duplicate
Comment:
bitten by the back button
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/242#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal
(by guest):
Probably the simplest fix for your problem is to run `macosx-app` after
the binary is installed, using the `postInst` hook. See
http://www.mail-archive.com/wxhaskell-
[EMAIL PROTECTED]/msg00129.html
-Judah
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/240#comment:1
(by duncan):
* platform: = Mac OS
Comment:
If you can figure out what Haskell code we can use to copy and preserve
this stuff that'd be great. I don't think it's ok to call out to an
external `cp` program.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/240#comment:2
Hackage
:
--+-
Comment (by duncan):
The Haddock module now has a function `haddockPackageFlags` that returns
all the `--read-interface=` flags.
I'm not quite clear about what the other options should be.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/241#comment
-1.13.3`. So by default we're still picking
the latest `HaXml` version but now we warn that we got inconsistent
versions.
In this example it would be possible to avoid the inconsistency by picking
`HaXml-1.13.3`. That is the next step.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket
don't have
consensus for stronger enforcement. I've created ticket #243 for Ian's
suggestion of notification emails.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/239#comment:8
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
#222: Hackage should be able to track which version of package is compatible
with
which version of GHC
+---
Reporter: guest |Owner:
Type: enhancement| Status: new
://hackage.haskell.org/trac/hackage/ticket/245
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
+---
Comment (by duncan):
An example we could automatically discover:
AutoForms-0.4 requires syb-with-class=0.4 but the latest version of syb-
with-class in hackage at the moment is 0.3.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/56#comment:4
another ticket or just send in a patch.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/211#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http
:
--+-
Changes (by [EMAIL PROTECTED]):
* summary: haddock2 is not passed -D__HADDOCK__ or cpp-options =
haddock2 is not passed cpp-options
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/238#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
#145: Hackage does not support UTF-8 characters
+---
Reporter: guest |Owner:
Type: defect | Status: new
Priority: normal |Milestone: Cabal
):
* priority: normal = low
* milestone: = _|_
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/245#comment:4
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http
the test stanza
also needs to declare what version of the test api interface it is using
since it is likely to be refined/improved over time.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/215#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
encouraging something which is wrong-headed or
pointless. It's not a big deal, but it shouldn't be warning about it.
--
gwern
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/247
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
. In
many legal jurisdictions it has no legal meaning and where it does one
usually has to disclaim any copyright interest explicitly.
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/247#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
/hackage/ticket/248
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
):
haddock 2.0 does not support the --hoogle option, sadly :-(. Perhaps
--hoogle with haddock 2 should give an error, or the haddocky people
should fix this up.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/249#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
://hackage.haskell.org/trac/hackage/ticket/250
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
):
Thanks for your quick replay.
Maybe the haddock guys should think about updating the output of haddock
--help.
(btw, the manual is indeed correct but I checked it too late).
Sorry for the noise.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/249#comment:2
Hackage http
/0.4/arrows-0.4.tar.gz
}}}
this would greatly simplify automating installs.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/251
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel
the tools correspond to. Any better suggestions to
make it a tad more generic?
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/227#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal
+---
Comment (by duncan):
Is it really useful to have the haddock interface for executables? Perhaps
we should just not try to copy it when installing?
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/250#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
'
in getModulePaths.
Cheers,
ar
ps: I must confess I don't get the reason for this difference so my
instinct would be to change preprocessSources (this is why I'm not
attaching any patch).
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/252#comment:1
Hackage http://haskell.org
. At the moment the OS is just a
String . We should decide if we want to use an enumeration or leave it
more flexible and just warn about unknown ones.
Checks are easy to add, see `Distribution/PackageDescription/Check.hs`
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/253
Hackage http
-arguments: for command
line arguments), and the error code is the number of tests fail, where
exitSuccess is equivalent to no failures. The log of the test run could
also be displayed on hackage.
Command line programs are simple, and can be written without learning a
new API. They can also
:
-+--
Changes (by mnislaih):
* status: new = assigned
* owner: = mnislaih
Comment:
I am working on this, wish me luck :)
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/223#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
/hackage/ticket/235#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
, and cabal will still treat it as a comment
and not try to interpret your crazy English stuff. It's a bit misleading.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/254
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
):
* status: new = closed
* resolution: = duplicate
Comment:
Argh. This looks like a duplicate of #89 so I will resolve this unless
somebody disagrees. (Eric)
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/255#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal
could just build-depends the library we
are currently trying to build. (One could also imagine a version
constraint like 'this version' which explicitly says to use the version
being built in this cabal file)
Thanks! (Eric Kow)
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket
):
Right, this is something that'd be nice, to allow the executables to
depend on the library within the package. I think that's exactly what #89
is about.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/255#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
.
}}}
Of course it does not help for older Cabal versions which lacked this
check but it's the best we can do and should help in future.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/120#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
a conditional dependency on the unix package.
Christian, what version of Solaris are you using and what does the above C
program report for you?
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/98#comment:15
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
-3.00$ uname -a
SunOS leo 5.10 Generic_127111-03 sun4u sparc SUNW,Sun-Fire-280R
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/98#comment:16
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
the minor issue that FieldDescr 'instances' are provided in
CabalInstall, whereas they would be required by Cabal already in
Distribution.Setup.hs
So they will need to be moved there.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/223#comment:2
Hackage http://haskell.org/cabal
:
-+--
Changes (by mnislaih):
* cc: [EMAIL PROTECTED] (added)
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/223#comment:3
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel
change `maxCommandLineSize` back to 30k which seemed to be ok
previously. I'm leaving the call to the `xargs` program well alone.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/98#comment:17
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
://hackage.haskell.org/trac/hackage/ticket/58#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-devel
` flag, or similar, to be needed if you want
the source from the RCS. Otherwise I'd expect it to give you the source
from the latest tarball.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/58#comment:8
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
:
+---
Comment (by igloo):
I think that Cabal is doing the right thing here. If your shell doesn't
expand ~ there, then Cabal shouldn't either.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:1
Hackage http
:
+---
Comment (by guest):
Ok, I guess that's fair. But maybe it should warn? It's never a sensible
thing to create a directory that starts with ~.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:2
Hackage
:
+---
Comment (by duncan):
Any consensus? Do we make the change or close the bug as wontfix?
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:4
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
this behaviour
was new to me. For me, the 'standard behaviour' is that ~ is expanded to
my home directory. Close it if you disagree that not expanding ~ is
standard behaviour.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:5
Hackage http://haskell.org/cabal/
Hackage: Cabal
with heuristic
tests, it will be unmanageable.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:7
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http
://hackage.haskell.org/trac/hackage/ticket/148#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
, an error would be appropriate.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:9
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org
prevent a user from specifying
anything that doesn't start with a drive letter.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:10
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/256#comment:12
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
is buildable
or not, I'd expect the sources to be included anyway, so the executable
can be built where it's buildable.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/257#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
:
+---
Comment (by [EMAIL PROTECTED]):
Indeed sdist shouldn't take any note of conditionals: it should pack all
of the files in any environment.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/257#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
/hackage/ticket/209#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
be
applied in either direction but I suspect many people read it in a
directed functional way. I have a feeling that the anonymous flag would
really throw people :-)
Perhaps we should ask opinions on the libraries list.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/209#comment:4
which has not
been unpacked yet.
}}}
We should think of sanity (and security) too, what if a link points
outside the working directory?
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/246#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
a problem like this...
--
gwern
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/89#comment:4
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org
, making greencard-lib depend on greencard. This was the
solution I used the last time I encountered a problem like this...
Sounds sensible.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/89#comment:5
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
] (added)
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/214#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
important. I'll have a look. - svein
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/214#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org
: http://hackage.haskell.org/trac/hackage/ticket/258
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
milestone.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/93#comment:4
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
+---
Changes (by duncan):
* status: new = closed
* resolution: = fixed
Comment:
We cannot actually remove it immediately but it is now on the way to being
deprecated because sdist and hackage now warn about its use.
--
Ticket URL: http
URL: http://hackage.haskell.org/trac/hackage/ticket/24#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-devel
+---
Changes (by duncan):
* milestone: Cabal-1.4 = Cabal-1.6
Comment:
Not ready for this release, punting.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/56#comment:5
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
releases on quality of release, to
motivate competetive uploaders to focus on quality rather than quantity of
uploads.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/259
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
as in .cabal files
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/260
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
-+--
Changes (by duncan):
* milestone: = Cabal-1.4
Comment:
Hmm, that's a surprise.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/260#comment:1
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
`
command, which takes all the flags for the underlying `configure` command.
It'll also need documenting.
Once the command line changes are done, the remaining task is easy.
Marking as such.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/88#comment:7
Hackage http://haskell.org/cabal
use them multiple times to get a list of dirs.
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/221#comment:7
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
cabal-devel@haskell.org
http
creates the archive using Hackage.Tar
we don't call setup sdist anymore but we use functions from
Distribution.Simple.SrcDist
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/40#comment:10
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
):
* milestone: = _|_
Comment:
Need more detail on requirements before we can do anything.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/196#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel
:
+---
Changes (by duncan):
* status: new = closed
* resolution: = fixed
Comment:
Already fixed but the ticket was not closed.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/257#comment:4
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
the internal flag --only so we can avoid building a setup
when build-type == Simple.
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/202#comment:2
Hackage http://haskell.org/cabal/
Hackage: Cabal and related projects___
cabal-devel mailing list
PROTECTED]
* Add --enable/disable-executable-stripping option
The default is enabled
Wed Mar 19 12:12:12 GMT 2008 Duncan Coutts [EMAIL PROTECTED]
* Documentation the --enable/disable-executable-stripping options
}}}
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/88#comment:8
:
+---
Changes (by duncan):
* milestone: Cabal-1.4 = Cabal-1.6
Comment:
Punting.
--
Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/209#comment:5
Hackage http://haskell.org/cabal/
Hackage: Cabal and related
''' so it doesn't
show up on the main Hackage listing.
If a newer package, with the same name, is uploaded then the older
packages will in effect be defunct. But if you don't have a newer package
with the same name, there is currently no way to get rid of packages
that are no longer valid
://hackage.haskell.org/trac/hackage/ticket/262
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
301 - 400 of 2948 matches
Mail list logo