Strange Design Decisions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I am trying to build a custom CentOS 5 install, including a custom group of
home-grown packages in addition to the standard CentOS package groups.  I'm
having trouble understanding some of the design changes that have taken place
between anaconda-runtime-10.1.1.63-4.centos4.1 and
anaconda-runtime-11.1.2.87-1.el5.centos.

Why was the <group> option to pkgorder removed?  In order to sort my own group
and its dependencies onto the first CD, it looks as if I now need either to hack
the pkgorder script, or break one of the CentOS groups.  Is that right, or is
there a better way of doing it?

Having hacked pkgorder, when I try to install I get a missing dependency:
"hicolor-icon-theme is needed by gtk2".  Now anaconda does pick up this
dependency - but deliberately ignores it: "ignoring hicolor-icon-theme>gtk2 in
whiteout".  What was the reason for deliberately breaking certain dependencies
with whiteout.py?  If anything, it's gtk2 that I would rather do without, since
I'm building a fileserver with a text-only interface.


Moray.
"To err is human.  To purr, feline"
http://members.aol.com/edgwddirk 


_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux