> > [Shamim writes about removing destroying our obsolete RPM's and
> > eliminating plans to provide RPM's in the future.]
>
> > Hmm, I am willing to nuke the obsolete RPM's, especially if
> > someone can provide me with a better set of Linux binary
> > distributions.
>
>I'm starting to think that a tarball to /usr/local/ is the most
>sane choice - it's distribution independent, and will even work on
>other Unix systems that can run Linux binaries (Well, ok, the *BSDs -
>although since OpenBSD is more and more becoming my primary dev
>platform, I will be happy to provide binaries.)
>
>The advantages claimed by formats like RPM are: i) easy installation
>ii) easy removal iii) dependency tracking
>
>The first is bogus (at least for Unicon) - anyone capable of writing
>code can certainly type "cd /; tar xzf unicon-10.1-binaries.tar.gz".
>The third is what has me irate - it only *tells* you about dependencies,
>it can't go fetch and install them; *and* the dependencies have
>dependencies, and... anyone tried to install anything substantial,
>like KDE or Mozilla/Galeon from RPMs? It's ridiculously painful.
>(The second? That's silly, who would uninstall Unicon?)
I agree except I would make it a tar of the lowest level directory.
Then you can say "cd /; tar zxvf ...", I can say "cd /local/unicon;
tar zxvf ...", followers of Bernstein can say "cd /apps/unicon; tar
zxvf ..." or whatever.
How about this:
Dist: config/unix/$(name)/status
tar cf - bin ipl | gzip >dist/unicon-$(name).tgz
I guess they still have to patch the binary, but that can be made more
user friendly.
>Brief *BSD plug: in contrast, if I set the env. variable PKG_PATH to a
>URL that has binaries (the *BSD equivalent of rpmfind.net) I can just
>say "pkg_add -v ${PKG_PATH}/package-name" - it will recursively
>install all dependencies. Something like debian's apt-get but even
>better, because packages and ports [built from source] know about each
>other so I can have a random mix of things installed as binaries and
>things I compiled myself.
I've never dealt seriously with RPM, but it sounds like it should have
been a shell script around tar if that's all it does. Even a shell
script could have handled automatically fetching dependencies though,
the FreeBSD ports collection is just (a lot of) make rules fer cryin'
out loud.
>Sorry for rambling. Anyway, the question for Linux is: which Linux?
>Which versions of the kernel and libc etc. are most popular? I have a
>spare machine that is only used to play NPR programs via RealAudio, I
>volunteer to install the blessed distribution on it and provide
>binaries.
>
>-s
SF compile farm is the way to go for that. Using the make rule above,
I bet you could build a distribution for every platform pretty easily.
ssh redhat
cd unicon; make X-Configure name=intel_linux Unicon Dist
ssh debian # Is this really necessary?
cd unicon; make X-Configure name=intel_linux Unicon Dist
ssh freebsd
cd unicon; make X-Configure name=intel_freebsd Unicon Dist
ssh solaris
cd unicon; make X-Configure name=sun4_solaris Unicon Dist
Blast everything in dist/ to the SF releases section.
Steve
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group
