“You aren’t gonna need it,” a general refrain when someone suggests
building functionality for the system that isn’t required by any current
user story. (from the XP FAQ, Extreme Programming (XP) FAQ — Jera Design LLC)
On Fri, 2003-06-13 at 10:26, Guillaume Marcais wrote:
What is YAGNI?
–
http://thispaceavailable.uxb.net/blog/index.html
To the systems programmer, users and applications serve only to provide a test load.
I don’t have much experience building RPMS, but if someone sent me a
template (and perhaps a walkthrough of the steps) I would be happy to
experiment with including this feature in raa-install.-Tom
Tom, I’d be happy to. Expect something from me this week and I’ll give
you more than you want to know about the Right Way of RPM complete with
some working code eventually.
Ari
Is it possible to create a .msi from a ruby program?
-Tom
On Fri, 2003-06-13 at 20:54, Aredridel wrote:
This is my biggest wish (thanks for articulating it so well, Ari).
You’re welcome.
I’ve got no idea how this sort of thing is handled in windows
.msi packages, not that I’d want to deal with creating them, or some
sort of installer-exe, or a .zip with a note on where in the tree to
unpack it. All are good options, though I think the .msi approach is
the “right way”.
Gentoo does a pretty good job with this - I like it anyway. I’ve also
been considering making raa-install generate gentoo ebuild files (RPM
specs were discussed on the list today too) which would make
raa-installa better gentoo citizen.
-Tom
On Sat, 2003-06-14 at 00:20, Jason Creighton wrote:
I want a package managers that adapts a package to the local configuration,
not one that basically dumps tarballs into the directory tree, assuming that
the package is built for the way the system is.
I'm just sick of seeing every Linux distro having its own little package manager. I'm sick of looking at the instructions for packaging something for distro X that goes something like this:“Prefix in /usr, don’t link against X, be sure to link against Y, etc, etc”.
ie, each distro has rules set out that each package must follow.
Why can’t we just have some metadata with each package describing what options
it supports. Then our package manager could just say to package X:“Okay, I want X11 support with GTK widgets, prefix is /usr/local, strip
binaries, don’t install the manpages, and install the package in
/tmp/lala-1234 so we can record what files are in the package before we
install it in /usr/local”.
You mean like Gentoo? 
The nice thing about this approach is that we would only have to package stuff
once. And then build the software differently for each configuration needed.
Yup! You want Gentoo.
I have vague ideas about
this software taking “steps” (download, extract, build, install) so that we
could take a package from any step and complete it. That is, we could have one
PC doing builds for a network of 100 that would pick up at the “install” step.
Or something like that.Also, how all the options a package has would be tricky to represent.
Take a look at Gentoo.
Daniel Carrera | OpenPGP fingerprint:
Graduate TA, Math Dept | 6643 8C8B 3522 66CB D16C D779 2FDD 7DAC 9AF7 7A88
UMD (301) 405-5137 | http://www.math.umd.edu/~dcarrera/pgp.html
On Sat, Jun 14, 2003 at 01:20:05PM +0900, Jason Creighton wrote:
Is it possible to create a .msi from a ruby program?
-Tom
An educated guess says “Yes, but not easily yet”.
I’ve been reading the Windows Installer SDK docs, but not coming up with
much I can look at, and I don’t have a license for the OS to actually
/use/ the tools, so…
I’ve alwas wanted to try Gentoo, but I don’t have the bandwidth.
Jason Creighton
On Sat, 14 Jun 2003 14:04:00 +0900 Tom Clarke tom@u2i.com wrote:
On Sat, 2003-06-14 at 00:20, Jason Creighton wrote:
I want a package managers that adapts a package to the local
configuration, not one that basically dumps tarballs into the directory
tree, assuming that the package is built for the way the system is.Gentoo does a pretty good job with this - I like it anyway.
Absolutely. For libraries, we’d request the path to the Ruby
installation and leverage that to either: (1) run the install.rb or (2)
install directly. I’m not sure why I’m presenting option (2).
MSI is commonly used in deploying applications on a web server.
Nullsoft’s installer is nice as well. There’s plenty of good options
that could be plugged into raa-install within a few hours.
_why