[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140712175249.GD25730@openwall.com>
Date: Sat, 12 Jul 2014 21:52:49 +0400
From: "(GalaxyMaster)" <galaxy@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: recent updates
On Sat, Jul 12, 2014 at 08:19:45PM +0400, gremlin@...mlin.ru wrote:
> Most of `make installworld` issues are easily fixed by splitting
> the installorder.conf lines. Some lines fail, but they are likely
> to succeed on a next iteration.
Well, I'm solving it a bit differently :). I usually just do something
like 'rpm -Uvh --root /owl *.rpm' and save the output of the
installation -- RPM resolves all dependencies and re-orders the packages
to meet the dependency tree. Then it's just a matter of following that
order and it's quite clear where a new package or a new dependency
should go.
Frankly, I still fail to understand why we are doing it manually instead
of relying on RPM's dependency solver. Personally, I'm not using 'make
installworld' at all: I have lists of packages I use for a specific
usage scenario and install them using just one transaction. It's quick,
resolves dependencies, and is nice looking. :).
> Should I step in to do that, or you'd like to do that yourself?
The primary issue was the extraction of the new RPM out of the
installation media. I've just committed my version of it (I'm not happy
about the way I did it, but it works).
I guess we need to drop all legacy stuff from installworld.sh now.
--
(GM)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
