Path to this page:
Next | Query returned 7 messages, browsing 1 to 10 | previous
CVS Commit History:
2025-03-05 04:40:14 by Masatake Daimon | Files touched by this commit (1173) |
Log message:
recursive revbump after patching lang/ghc910
|
2025-02-02 14:06:08 by Masatake Daimon | Files touched by this commit (1173) |
Log message:
Bump all Haskell packages after switching the default compiler.
|
2025-02-02 03:59:31 by Masatake Daimon | Files touched by this commit (3) |  |
Log message:
sysutils/hs-filepath-bytestring: update to filepath-bytestring-1.5.2.0.2
filepath-bytestring (1.5.2.0.2) unstable; urgency=medium
* Relax bounds to allow base-4.20 (ghc 9.10.1).
-- Joey Hess <id@joeyh.name> Mon, 20 Jan 2025 19:42:24 -0400
filepath-bytestring (1.5.2.0.1) unstable; urgency=medium
* Relax bounds on filepath to all versions for which test suite passes.
-- Joey Hess <id@joeyh.name> Mon, 20 Jan 2025 14:06:54 -0400
filepath-bytestring (1.5.2.0.0) unstable; urgency=medium
* Update to correspond to filepath-1.5.2.0, which fixes a bug
introduced in filepath-1.4.100.2.
* normalise C:\\\\ to C:\
-- Joey Hess <id@joeyh.name> Tue, 06 Feb 2024 10:33:31 -0400
|
2024-05-09 03:32:57 by Masatake Daimon | Files touched by this commit (1137) |
Log message:
Recursive revbump after changing the default Haskell compiler
|
2024-04-28 13:48:16 by Masatake Daimon | Files touched by this commit (2) |
Log message:
sysutils/hs-filepath-bytestring: Fix build with GHC 9.8
This breaks build with the currently default GHC 9.6. Please bear with me
until I switch the default compiler.
|
2023-11-02 07:37:49 by Masatake Daimon | Files touched by this commit (1141) |
Log message:
Revbump all Haskell after updating lang/ghc96
|
2023-10-24 10:19:49 by Masatake Daimon | Files touched by this commit (5) |
Log message:
sysutils/hs-filepath-bytestring: import hs-filepath-bytestring-1.4.2.1.13
This package provides functionality for manipulating RawFilePath values. It
can be used as a drop in replacement for the filepath library to get the
benefits of using ByteStrings. It provides three modules:
* System.FilePath.Posix.ByteString manipulates POSIX/Linux style
RawFilePath values (with / as the path separator).
* System.FilePath.Windows.ByteString manipulates Windows style RawFilePath
values (with either \ or / as the path separator, and deals with drives).
* System.FilePath.ByteString is an alias for the module appropriate to your
platform.
All three modules provide the same API, and the same documentation (calling
out differences in the different variants).
|
Next | Query returned 7 messages, browsing 1 to 10 | previous