1 |
I am not sure if i can understand exactly, what you are speaking here. |
2 |
|
3 |
This will be somewhat half-thought idea here, but.. |
4 |
|
5 |
As much as i have got, system contains packages nessecary for me and |
6 |
world is all what i have emerged? And system comes basically from |
7 |
profile? |
8 |
|
9 |
For me as an user, there is no differences between "system", "world" |
10 |
and "kde-meta" (syntactically), except that world will contain |
11 |
kde-meta after i have emerged it and system will contain packages from |
12 |
my selected profile. |
13 |
|
14 |
Now, wouldnt it be good if they were exactly the same thing on system |
15 |
level, and all configureable? |
16 |
|
17 |
Lets imagine configuration file with the following syntax: |
18 |
# System points to x86 |
19 |
System=>System x86 2.6 |
20 |
# World is included from another file |
21 |
@world.list |
22 |
[system] |
23 |
#system contains an additional package "moo" |
24 |
++moo |
25 |
[world] |
26 |
#world.list file may contain "moo", but not world |
27 |
--moo |
28 |
[kde-meta] |
29 |
++kicker |
30 |
|
31 |
Those files could be called patches and optionally contain includes |
32 |
from random servers. |
33 |
|
34 |
2006/3/21, Brian <dol-sen@×××××.net>: |
35 |
> I remember that a while back I asked about user created package lists to |
36 |
> supplement system & world. If I remember correctly, I believe you |
37 |
> (portage devs) were open to the idea. |
38 |
> |
39 |
> I have been working on re-coding the upgrades view in porthole partially |
40 |
> to get around a gtk treeview bug causing segfaults (reportedly fixed in |
41 |
> >=gtk+-2.8.14). The other reason is to add a feature I have thought |
42 |
> about for some time (the reason I asked this last time). Anyway I have |
43 |
> the basic re-coding done. It is now possible to break down the |
44 |
> upgradeable packages into as many lists as desired. |
45 |
> |
46 |
> Currently lists are hard coded but will be configurable. (Easier to get |
47 |
> one thing working at a time) "System" list is generated at run time |
48 |
> (using the self.system_cmd, then using portage.catsplit to trim the |
49 |
> version info): |
50 |
> |
51 |
> self.cat_order = ["System", "User list1", "World", "Dependencies"] |
52 |
> self.categories = {"System":None, "World":"World", "User list1":None, "Dependencies":"Dependencies"} |
53 |
> self.upgradables = {} |
54 |
> self.pkg_count = {} |
55 |
> for key in self.categories: |
56 |
> self.upgradables[key] = {} |
57 |
> self.pkg_count[key] = 0 |
58 |
> self.count = 0 |
59 |
> # command lifted fom emwrap and emwrap.sh |
60 |
> self.system_cmd = "emerge -ep --nocolor --nospinner system | cut -s -f2 -d ']'| cut -f1 -d '[' | sed 's/^[ ]\+//' | sed 's/[ ].*$//'" |
61 |
> |
62 |
> [snip] |
63 |
> |
64 |
> upgradable = package.is_upgradable() |
65 |
> if upgradable: # is_upgradable() = 1 for upgrade, -1 for downgrade |
66 |
> if upgradable == 1 or not self.upgrade_only: |
67 |
> for key in self.cat_order: |
68 |
> if package.in_list(self.categories[key]): |
69 |
> self.upgradables[key][package.full_name] = package |
70 |
> self.pkg_count[key] += 1 |
71 |
> break |
72 |
> |
73 |
> |
74 |
> Is there any plans for officially supported user lists? eg: |
75 |
> |
76 |
> # emerge -up --list mylist |
77 |
> |
78 |
> where mylist is in /etc/portage/lists/ (for example) |
79 |
> |
80 |
> Should I set it up to use them from /etc/portage/lists/. Or just from a |
81 |
> users .porthole directory? I may have missed it if it has already been |
82 |
> done :) |
83 |
> |
84 |
> |
85 |
> -- |
86 |
> Brian <dol-sen@×××××.net> |
87 |
> |
88 |
> -- |
89 |
> gentoo-portage-dev@g.o mailing list |
90 |
> |
91 |
> |
92 |
|
93 |
|
94 |
-- |
95 |
tvali |
96 |
|
97 |
>From a programmer's point of view, the user is a peripheral that types |
98 |
when you issue a read request. -P. Williams |
99 |
|
100 |
If you think your management doesn't know what it's doing or that your |
101 |
organisation turns out low-quality software crap that embarrasses you, |
102 |
then leave. -Ed Yourdon |
103 |
|
104 |
We all agree on the necessity of compromise. We just can't agree on |
105 |
when it's necessary to compromise. -Larry Wall |
106 |
|
107 |
[ http://www.softwarequotes.com/ ] - |
108 |
http://www.softwarequotes.com/ShowQuotes.asp?ID=544&Name=Borenstein,_Nathaniel_S. |
109 |
- http://www.softwarequotes.com/ShowQuotes.asp?ID=571&Name=Boehm,_Barry |
110 |
|
111 |
-- |
112 |
gentoo-portage-dev@g.o mailing list |