if it s possible i d like to get more generique target for emerge
like ones that would allow to fetchonly stable builds , and an other for most used builds ,and one for all the latests stable builds , in order to be able to run emerge -f <target> and have a pack of downloaded packages ready for a local network, the
You mean like this?
yes like this, but, already defined ones.
Right now i can only supose than gnome kde and mozilla are commonely used by 80% of the user so i want them , but i dont want the linux gazette as there may be only 1 guy who ll use it so i ll wait for him to download it in order it comes in my portage cache.
Servers have tools wich generates stats of downloaded files , making a generic target of the let s say 200 most downloaded packages would be nice, as well as re-using the target for keeping packages up do date, in order i already do have the distfiles before users want them( not sure if this is a very good explaination).
In the same idee once a month i might want to get all the stable builds as they are what users pulls the most ( i think ) but i d ont want to pull unstable ones ( wich i would do if i was using rsync), manualy defining new generic target would require me to watch all the times new ebuilds in order for me to manualy add thoses.
Also something for deleting unused distfiles would be nice for exemple the man pages can only be stable as they are text, if i keep updating i ll keep all the unused distfiles whereas the only intersant one is the latest, this case is easy , but when packages have dependencies it s hard to know wich packages have an older version wich can never be pulled whatever other package i emerge.
perhaps i am very wrong and there s tools wich allow to do this, but ... i didn t found them.
not sure i explained myself very well lack of english skills i guess.
No. When sets are available, you may use public ones or make your own.
It does not make sense to make arbitrary lists of non-installable sets.