TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Effing Package Management

27 点作者 dominis超过 13 年前

6 条评论

ajross超过 13 年前
Yet another attempt to abstract things that cannot be abstracted. Works as long as your "package" is a blob of files. Doesn't seem to understand anything else. Some package management systems allow dependencies (on other packages, on files, or on abstracted "capabilities") that are inherently system-dependent.<p>All this provides vs. using plain tarballs (or even "make install") is the ability to back out and upgrade your custom packages using your system's package management command.
评论 #3330554 未加载
评论 #3330679 未加载
joeyh超过 13 年前
I suppose it's nice that <a href="http://kitenet.net/~joey/code/alien/" rel="nofollow">http://kitenet.net/~joey/code/alien/</a> finally has some competition. ;)<p>I'm unsure of the wisdom of conflating package format conversion (rpm, deb, puppet) with package building (from gem or python sources).
serverascode超过 13 年前
I think this is effing awesome, and will be trying it out soon.<p>Don't understand why devs use apt-get/yum to run their linux desktop but often code their app in such a way that it can't be managed with OS level packaging. Don't imagine a lot of developers manage their own personal linux distro. Probably some... :)
评论 #3331131 未加载
评论 #3331031 未加载
draegtun超过 13 年前
Also see Acmeist <i>Package</i> which allows you to create packages in CPAN, PyPI and Ruby Gems.<p>ref: <a href="https://metacpan.org/module/Package" rel="nofollow">https://metacpan.org/module/Package</a> &#38; <a href="http://acmeism.org/projects/" rel="nofollow">http://acmeism.org/projects/</a>
serverascode超过 13 年前
Just used this today to create rpms from the rubygems-mirror and it's dependencies so that I could install on a redhat server and mirror rubygems.org for local builds.<p>Worked great.
binarycrusader超过 13 年前
The 'solaris' option is a bit bogus though; it should be named 'SVR4'. As of Solaris 11, SVR4 packages are no longer the expected package format.