"G. Matthew Rice" <[EMAIL PROTECTED]> wrote: > Someone commented last week that we should be testing more than > just apt-get for the deb side of the exam. > My questions on that side are, should we: > 1. test awareness of the apt-* tool set? > 2. test ability to use the apt-* tool set? > 3. dump dselect? :)
Test DPKG when you test RPM. Test APT when you test YUM. APT !~ RPM, APT ~ YUM. ;) And if you consider Portage, then test it when you test for APT/YUM (not DPKG/RPM). I'm not saying you should test these, I'm just saying they are the relationships between the different packging tools (and port-source in the case of Portage). > On the RPM side, we aren't testing an equivalent to apt-get. > Should we add in yum (or something else)? You should _always_ test YUM if you test APT. You should _always_ test DPKG if you test RPM. People who use DPKG systems use APT. People who use RPM systems use YUM. I haven't used RPM directly in a long time. > Someone (Bryan?) also commented that the yum level could be > justified in moving to LPIC-2? No, I'd do the opposite! Put basic APT and YUM in LPIC-1. Put advanced DPKG and RPM resolution in LPIC-2. > Does anyone else feel this way? That would lead > me to think that apt-get should be moved to LPIC-2, as well. > I know. The horror. I use apt-get 50-100 times for every > once that I use dpkg. That's what YUM users say about RPM. ;) > Or did I misread that comment? Yes, you did, but that's okay. You were just asking questions, and I now answered. -- 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
