On Tue, 2006-21-03 at 16:44 +0200, tvali wrote: > I am not sure if i can understand exactly, what you are speaking here. >
Say an admin has a server setup and wants an easy way to monitor a certain group of packages for updates so he/she can choose to ignore or update. my list = [apache, mod_1, mod_2, mysql, webapp1, webapp2,...] having them grouped into one list and doing an: # emerge -up --list mylist would indicate easily if any packages in the special list are upgradable irregardless of whether it is in world, system, whatever. > This will be somewhat half-thought idea here, but.. > > As much as i have got, system contains packages nessecary for me and > world is all what i have emerged? And system comes basically from > profile? > > For me as an user, there is no differences between "system", "world" > and "kde-meta" (syntactically), except that world will contain > kde-meta after i have emerged it and system will contain packages from > my selected profile. > Now, wouldnt it be good if they were exactly the same thing on system > level, and all configureable? > > Lets imagine configuration file with the following syntax: > # System points to x86 > System=>System x86 2.6 > # World is included from another file > @world.list > [system] > #system contains an additional package "moo" > ++moo > [world] > #world.list file may contain "moo", but not world > --moo > [kde-meta] > ++kicker > > Those files could be called patches and optionally contain includes > from random servers. > too early in the morning to follow that. > -- Brian <[EMAIL PROTECTED]> -- [email protected] mailing list
