1 |
Howdy, |
2 |
Well, actually, yes, in a way. The other confusion was what, exactly, I |
3 |
needed to put into the package.keywords file. Depend atoms can apparently |
4 |
be of several somewhat specific formats, and I wasn't sure which applied in |
5 |
that case. I'm refering to the ability to specify specific versions, |
6 |
specific versions or greater, etc. |
7 |
Thanks, |
8 |
Zack. |
9 |
|
10 |
----- Original Message ----- |
11 |
From: "William Hubbs" <williamh@g.o> |
12 |
To: <gentoo-accessibility@l.g.o> |
13 |
Sent: Thursday, March 01, 2007 9:30 PM |
14 |
Subject: Re: [gentoo-accessibility] out-of-date ebuilds? |
15 |
|
16 |
|
17 |
> -----BEGIN PGP SIGNED MESSAGE----- |
18 |
> Hash: SHA1 |
19 |
> |
20 |
> Hi Zack, |
21 |
> |
22 |
> the ebuild version numbers are the same as the version numbers of the |
23 |
> packages, unless there is a gentoo specific revision number attached. |
24 |
> The gentoo revision number would be a "-r" followed by a number at the |
25 |
> end of the version number, such as emacspeak-25-r2. |
26 |
> |
27 |
> Is that the thing that was confusing you about our ebuild version |
28 |
> numbers? |
29 |
> |
30 |
> Thanks, |
31 |
> |
32 |
> William |
33 |
> |
34 |
> On Thu, Mar 01, 2007 at 08:10:08PM -0800, Zachary Kline wrote: |
35 |
>> Hi, |
36 |
>> I was familiar with this process, just didn't think it applied to |
37 |
>> these |
38 |
>> particular packages. The ebuild version specification system is a bit |
39 |
>> tough to get used to: version numbers in particular. |
40 |
>> Thanks! |
41 |
>> Zack. |
42 |
>> |
43 |
>> ----- Original Message ----- |
44 |
>> From: "William Hubbs" <williamh@g.o> |
45 |
>> To: <gentoo-accessibility@l.g.o> |
46 |
>> Sent: Thursday, March 01, 2007 8:05 PM |
47 |
>> Subject: Re: [gentoo-accessibility] out-of-date ebuilds? |
48 |
>> |
49 |
>> |
50 |
>> >-----BEGIN PGP SIGNED MESSAGE----- |
51 |
>> >Hash: SHA1 |
52 |
>> > |
53 |
>> >Hi Zack, |
54 |
>> > |
55 |
>> >first off, are you familiar with the masked packages and how to use |
56 |
>> >them? Some of the packages you want might not be marked stable yet. |
57 |
>> > |
58 |
>> >Basically, if you want to use something that isn't stable, you can do |
59 |
>> >something like this: |
60 |
>> > |
61 |
>> >echo app-accessibility/emacspeak >> /etc/portage/package.mask |
62 |
>> > |
63 |
>> >You can substitute any other package you want to use for |
64 |
>> >app-accessibility/emacspeak, it was just an example. If there are new |
65 |
>> >versions of packages that you know about that are not in the tree, you |
66 |
>> >can file a bug at http://bugs.gentoo.org and request a version bump for |
67 |
>> >the package. |
68 |
>> > |
69 |
>> >The way to get things moved to stable is to use them and report problems |
70 |
>> >to the bugzilla address I gave above. If packages do not have bugs |
71 |
>> >open, they will eventually be marked stable. |
72 |
>> > |
73 |
>> >Thanks, |
74 |
>> > |
75 |
>> >William |
76 |
>> > |
77 |
>> >On Thu, Mar 01, 2007 at 06:56:19PM -0800, Zachary Kline wrote: |
78 |
>> >>Hello, |
79 |
>> >> (For some reason my emails to the list haven't been getting through |
80 |
>> >>using my old address, so I subscribed this one...) |
81 |
>> >>I've noticed that several accessibility-related ebuilds are out of sync |
82 |
>> >>with the latest available from the upstream sources. Orca comes to |
83 |
>> >>mind, |
84 |
>> >>as does Emacspeak and Speechd-El. I'm not terribly familiar with the |
85 |
>> >>Gentoo ebuild creation process, nor with who, if anyone, is supposed to |
86 |
>> >>maintain these. I do notice, for instance, that Orca is at 2.1 |
87 |
>> >>upstream |
88 |
>> >>and 1.00 here. I don't want to fall behind, if possible, in terms of |
89 |
>> >>features and such. |
90 |
>> >>Is this an issue which I should report elsewhere? Should I try to make |
91 |
>> >>ebuilds for these packages myself? |
92 |
>> >>Thanks much, |
93 |
>> >>Zack. |
94 |
>> >> |
95 |
>> >>_________________________________________________________________ |
96 |
>> >>Find a local pizza place, movie theater, and more?.then map the best |
97 |
>> >>route! |
98 |
>> >>http://maps.live.com/?icid=hmtag1&FORM=MGAC01 |
99 |
>> >> |
100 |
>> >>-- |
101 |
>> >>gentoo-accessibility@g.o mailing list |
102 |
>> >> |
103 |
>> > |
104 |
>> >- -- |
105 |
>> >William Hubbs |
106 |
>> >gentoo accessibility team lead |
107 |
>> >williamh@g.o |
108 |
>> >-----BEGIN PGP SIGNATURE----- |
109 |
>> >Version: GnuPG v1.4.6 (GNU/Linux) |
110 |
>> > |
111 |
>> >iD8DBQFF56KkblQW9DDEZTgRAun9AJwOutDSR7+k/gHI4iHly+B+idzInwCfdD13 |
112 |
>> >90cpB8MWyMsHDIHxLDXKF20= |
113 |
>> >=QtQd |
114 |
>> >-----END PGP SIGNATURE----- |
115 |
>> >-- |
116 |
>> >gentoo-accessibility@g.o mailing list |
117 |
>> > |
118 |
>> > |
119 |
>> |
120 |
>> -- |
121 |
>> gentoo-accessibility@g.o mailing list |
122 |
>> |
123 |
> |
124 |
> - -- |
125 |
> William Hubbs |
126 |
> gentoo accessibility team lead |
127 |
> williamh@g.o |
128 |
> -----BEGIN PGP SIGNATURE----- |
129 |
> Version: GnuPG v1.4.6 (GNU/Linux) |
130 |
> |
131 |
> iD8DBQFF57aLblQW9DDEZTgRAp83AJ9RvzV7foSvoou7wXq+Va5SeNZUSACglc37 |
132 |
> XgKeB10vH1x1iTLEFXh55GM= |
133 |
> =RoML |
134 |
> -----END PGP SIGNATURE----- |
135 |
> -- |
136 |
> gentoo-accessibility@g.o mailing list |
137 |
> |
138 |
> |
139 |
|
140 |
-- |
141 |
gentoo-accessibility@g.o mailing list |