是否有适合维护 Cabal Haskell 包的变更日志的工具?
我正在快速而激烈地为编译器编写者开发一个新的 Haskell 包。我每天都会查看许多次要版本号,而 Haskell 打包系统 Cabal 则不会似乎没有提供任何用于更新版本号或维护更改日志的工具。 (日志将进入 git ,但使用该软件包的任何人都看不到。)我会杀死相当于 Debian 的 uupdate 或 dch 的东西/ debchange
工具。
有谁知道可用于自动增加版本号并向更改日志添加条目的通用工具?
I'm working fast and furiously on a new Haskell package for compiler writers. I'm going through many minor version numbers daily, and the Haskell packaging system, Cabal, doesn't seem to offer any tools for updating version numbers or for maintaining a change log. (Logs are going into git
but that's not visible to anyone using the package.) I would kill for something equivalent to Debian's uupdate
or dch
/debchange
tools.
Does anyone know of general-purpose tools that could be used to increment version numbers automatically and add an entry to a change log?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我使用一个非常简单的方案来生成我的
CHANGELOG
。我只是向darcs
请求它,并将其包含在我的包的.cabal
文件的extra-files
部分中。不过,这对于您的要求来说似乎太简单了。 =)也就是说,您可以更进一步,使用自定义 cabal
Setup.(hs|lhs)
在cabal sdist
期间构建CHANGELOG
code> 从您的darcs
或git
存储库的提交信息(或您决定用来跟踪它的任何系统)中删除Setup.lhs
由darcs
使用,做了非常相似的事情包括有关版本号和自上一个版本以来应用的补丁数量的信息。查看Setup.lhs
以了解如何完成此操作。I use a very simple scheme to generate my
CHANGELOG
. I just askdarcs
for it and include it in theextra-files
section of my package's.cabal
file. Though, this seems too simplistic for what you are asking. =)That said, you can go quite a bit farther and use a custom cabal
Setup.(hs|lhs)
that builds theCHANGELOG
duringcabal sdist
out of yourdarcs
orgit
repository's commit info (or out of whatever system you decide to use to track it)The
Setup.lhs
used bydarcs
does something very similar to include information on version numbers and number of applied patches since the last version. Look at thesdistHook
andgenerateVersionModule
machinery inSetup.lhs
to get an idea of how this can be done.为了不回答你的问题,我什么都不知道。这听起来很适合在 Haskell Proposals subreddit 中发布,因为它看起来像是非常有用的想法。
To non-answer your question, I'm not aware of anything. This sounds like a good match for posting in the Haskell Proposals subreddit, since it seems like a pretty useful idea.