Bart Van Loon <[EMAIL PROTECTED]> wrote:
> for the sake of completeness, on Gentoo it would be
> ebuild in the rpm, dpkg camp
> emerge in the yum, apt camp

Actually, I shouldn't have done ...
  DPKG ~ RPM (~ source)

That was incorrect.  E.g., rpmbuild ~ source, not "rpm".  I
over-simplified, including relating all of Portage (not just emerge)
to APT and YUM.

But since ebuild does apply to installing binaries as well as
building, it does apply to DPKG ~ RPM ~ ebuild.

In any case, thank you for correcting my over-simplification that was
actually wrong from the point of detail.

At some point there has to be a reconsideration of how much we're
going to address packages (most Linux distros) v. ports (most BSD, as
well as Gentoo's "ports on steroids" approach ;) and decide what we
are and are not going to cover.

And most importantly, as with all things LPI, we really have to have
people who have broad, cross-distro experience.  I know that's hard
to come by at times or, even worse yet, avoiding the
over-simplifications (as I just did ;).

But one thing is for certain, APT !~ RPM, APT ~ YUM.  The RPM-centric
focus has got to go.  E.g., I use "yum localinstall" and "yum remove"
instead of "rpm -Uhv" and "rpm -e", respectively.  I only go to RPM
when I have a situation that absolutely forces me away from YUM, much
like why I use DPKG when a similar situation with APT appears.

I honestly think it's time to consider Basic Emerge coverage along
with APT and YUM in LPIC-1.  You can still put DPKG and RPM in LPIC-1
(possibly with ebuild), but for the most part, they are used for
little more than advanced package resolution -- so either a "hard"
LPIC-1, or possibly LPIC-2 (I didn't suggest that like previously
stated, but it's not actually a bad idea).

But RPM has got to go as the equivalent to APT, they are not relevant
and not used today at all.

-- 
Bryan J. Smith   Professional, Technical Annoyance
[EMAIL PROTECTED]    http://thebs413.blogspot.com
--------------------------------------------------
     Fission Power:  An Inconvenient Solution
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev

Reply via email to