1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Tue, 29 Apr 2003 19:45:43 +0200 |
5 |
Henti Smith <bain@×××××××.za> wrote: |
6 |
|
7 |
> On Tue, 29 Apr 2003 19:44:41 +0000 |
8 |
> Mikael Andersson <snikkt@×××××.com> wrote: |
9 |
> |
10 |
> > Gentoo is moving to slow this is why this kind of ideas emerge. It |
11 |
> > might be moving fast, but obviously still too slow for many. I've |
12 |
> > got a few ebuilds done which i haven't even bothered to try to get |
13 |
> > in since i've seen the queue in bugzillla and I'm sure several |
14 |
> > others are in the same situation. |
15 |
|
16 |
Actually I've had one or two of my ebuilds added no prob. I did recieve |
17 |
one warning to remember to include a change log. Which I fixed with one |
18 |
ebuild and I need to do for some others I made. I'm also going to |
19 |
update a few of them. I've been very busy this week offline which is |
20 |
why I've not got to it all yet. When I upload ebuilds to bugzilla I |
21 |
also include the digests as well. I'm not sure if that helps it along. |
22 |
One thing I do need to figure out for ebuilds is putting in multiple |
23 |
URI's as some packages come from source forge and they offer multiples. |
24 |
I put in my default at the time. |
25 |
|
26 |
With a few people I think there were conflicts over packages(ie two |
27 |
diffrent people submit packages not realizing someone just did submit |
28 |
one). I know that seemed to be the case with limewire. While the |
29 |
newest package for that one was more complex et al it still relied on |
30 |
"${P}" and well limewires tar doesn't have a version number so at least |
31 |
for me that wouldn't build but the earlier ebuild worked just fine. |
32 |
I'm not sure (ok I didn't pay attention I'll admit that) if buzilla is |
33 |
searching message bodies or only subjects. If it's only subjects |
34 |
perhaps if it searched bodies that would make it more appearant on a |
35 |
search if something exists already. |
36 |
|
37 |
> > Communication between developers and users is always hard. Esp since |
38 |
> > many gentoo users isn't strictly users. Some of the points i make |
39 |
> > might sound a bit harsh - but try to smile while you read them - i |
40 |
> > think it will make gentoo a better distribution if you do .) |
41 |
> |
42 |
> Personally .. I think a good "how to build ebuilds" would help alot if |
43 |
> not a ebuild spacific mailling list. This way I can submit questions I |
44 |
> have or ebuild for testing before submitting them to bugzilla ... |
45 |
|
46 |
I got told by someone to do "man 5 ebuild" but prior to that all I had |
47 |
was looking in others ebuilds to get an idea or looking at the online |
48 |
howto. I think it would help if it was in condensed form showing the |
49 |
most commonly used bits and how to use them. Tho to some extent I |
50 |
suppose the online howto already does that. |
51 |
|
52 |
Btw I'm one of those people who I guess gets bored and surfs |
53 |
stable.gentoo.org or portage on my drive and looks for unstables/masked |
54 |
that might prove intresting. Weather or not I use them in the long run |
55 |
I do try several and report on how they function on stable.gentoo in |
56 |
hopes that more packages get added to the database. I think more people |
57 |
need to participate in ranking packages and that might help shove them |
58 |
into the tree faster. |
59 |
|
60 |
As for nix experience. I'm self taught from hands on. Granted I |
61 |
started from mandrake 6.5 and quit it at 9(it was definitly nix |
62 |
bloatware tho good for newbies) moving to gentoo. I'm now learning much |
63 |
more as life the past few years was hecktic(my daughter died last august |
64 |
from brain cancer at age 12). Anyways I'm gradually going to be |
65 |
teaching myself a few other distros(just built 2 486's... one to use for |
66 |
debian and another to use for freebsd). I don't know what I'd get |
67 |
classed (as ok I duel book with 2k as well)... But on the plus side I |
68 |
did take programming in the 80's granted though not used that in so long |
69 |
I can barely remember it. :/ |
70 |
|
71 |
Anyways yes probably many are just installing and being done with it. |
72 |
ie going only with the stables or going fully with the unstables. They |
73 |
want no hassle but it to just work. |
74 |
|
75 |
> I use existing ebuilds as a base for new ones since the skel in |
76 |
> /usr/portage is really not that helpfull when you doin git for the |
77 |
> first time. Maybe change skel can be a fully functional ebuils to do |
78 |
> ummm .. nothing .. but have valid and correct ebuild structures and |
79 |
> ways of doing things to help guide a new ebuilder in the right |
80 |
> direction. |
81 |
|
82 |
I made myself a template frankly and I keep my finished/submitted |
83 |
ebuilds in a finished work directory for refrence at what I did to get |
84 |
whatever going right. But there are also a few other skel's one for the |
85 |
changelog at least. But I too have looked in others existing trying to |
86 |
figure out how to make things work. I wanted to make an ebuild for |
87 |
hackedbox(blackbox varient with no slit and no toolbar; that is slimed |
88 |
down) and saw that there was a specific eclass for *box family. But the |
89 |
ebuild failed at one spot.(amusingly it was something about "Bloat_IT" |
90 |
in the error... the bloat option for that window manager adds in the |
91 |
slit and toolbar) |
92 |
|
93 |
> I've had ebuilds that does wierd things that I don't understand .. and |
94 |
> have asked for comments in bugzilla and on devel list but got no |
95 |
> reply. |
96 |
> |
97 |
> this makes it hard to understand what I'm doing wrong or right .. |
98 |
|
99 |
Oh I know that one too. I was asking questions on the gentoo user list |
100 |
about that. But saw this one reciently and thought maybe I should take |
101 |
such talk here and people in this list are probably the ones doing |
102 |
ebuilds anyways. |
103 |
|
104 |
|
105 |
> I think the suggestion of a ebuild mailling list for ebuild developers |
106 |
> could be helpfull here as well. |
107 |
|
108 |
Yes tho to some extent I thought that was somewhat what this was. |
109 |
Unless this is ment more for those doing the base/core packages for |
110 |
gentoo. I think it would be handy tho if we had a spot to show are |
111 |
ebuilds and say how does this look? It's working good for me would |
112 |
someone like to try it? |
113 |
|
114 |
|
115 |
> The time it takes to get feedback is discouraging ... I have helped |
116 |
> with the ebuild for openexr and since then a new version has been |
117 |
> released which I submitted and then an update to work with |
118 |
> nv-cg-toolkit and the NVSDK and still no feedback ... |
119 |
|
120 |
I've gotten reasonable enough feedback but mind you that was typically |
121 |
regarding regular bugs not ebuilds. But I do see when ebuilds get |
122 |
shifted from one gentoo bug wrangler to another as they take a peak at |
123 |
it. When my first ebuild got added to the tree (wmmsg) I did get a note |
124 |
saying good job as well as remember to include change logs on another |
125 |
ebuild(I think it was another and not the wmmsg one ... I'd have to dig |
126 |
in my bugs email to see for sure). Right now I'm slowly working on a |
127 |
few ebuilds. A few I abandoned because they were just weird and I |
128 |
didn't know what the heck to do to get around the errors in question. |
129 |
One I've finished making but can neither build nor submit affects |
130 |
several other packages I'm making as they depend on a ebuild which is |
131 |
masked due to some issues it has.(either it was libtool or autoconf or |
132 |
both are masked. I need autoconf 2.5 and the 1.4.2 libtool) |
133 |
|
134 |
|
135 |
> I understand there are things happening to correct this and I'm |
136 |
> waiting in antisipation for those changes as the only real |
137 |
> contribution I can make to gentoo is bug reporting and ebuilds ... I'm |
138 |
> doing lots of bug reporting ... but only one ebuild I had any |
139 |
> interaction with has been incorporated into the tree. |
140 |
|
141 |
I'm doing about the same. |
142 |
|
143 |
> If you meet a hungry man and give him a fish .. he eats for a day ... |
144 |
> give him a fishing rod and he eats for a live time I knwo it's |
145 |
> cliche'd .. but it's because it's true .. |
146 |
|
147 |
Well people will build ebuilds out of attachment to programs that they |
148 |
miss or due to things not meeting what they require. Mind you I've done |
149 |
several ebuilds just for the heck of it. To hopefully expand what is |
150 |
available and be of use to someone. That is why I've taken on trying to |
151 |
make some ham radio ebuilds as tho I'm a ham radio operator(licensed for |
152 |
VHF) I'm unlikely to use it(as it is typically for people with HF) but I |
153 |
noticed a few ham radio operators also using gentoo. I figured packages |
154 |
in that line would be used. As well I made some that looked |
155 |
intresting(in the amusing sense or in the useful sense). |
156 |
|
157 |
> It will take alot less effort in the long run to help a "new" |
158 |
> developer get it right and then monitor him to make sure he knows what |
159 |
> he's doing then he can maintain he's own package. |
160 |
|
161 |
True. If we know what we are doing and we know the packages we've made |
162 |
it isn't a big deal to bump them. Unless the program itself has |
163 |
undergone major revision and the ebuild has to change alot to deal with |
164 |
that. But again if they understand things it's likely to be less a |
165 |
problem. |
166 |
|
167 |
> I do however thing a proper document on how to create correct ebuilds |
168 |
> will go along way to helping ebuilders do things right. What is |
169 |
> required etc etc. Sinply reading the emerge and ebuild documentation |
170 |
> is not enought to understand the inner workings of the ebuild, and it |
171 |
> has changed quiet a bit in the last few months. |
172 |
|
173 |
have you done "man 5 ebuild"? That has far more listed command wise |
174 |
than the online howto. Tho somethings I'm still wondering what the heck |
175 |
it means(syntax or usage as not everything has an example... as well as |
176 |
I've been out of doing any sort of programming for many years so I |
177 |
probably admittedly need a refresher course on the lingo) |
178 |
|
179 |
> Once again I suggest a ebuild mailling list with the sole use of |
180 |
> creating discussing and testing new ebuilds .. |
181 |
|
182 |
Question here as I am new to this list(though have posted on gentoo user |
183 |
and gentoo desktop). Isn't this list for that to some extent? For |
184 |
making ebuilds and general gentoo development? Or what is the exact |
185 |
usage of this list to be? I know there was a like discussion in the |
186 |
security list(frankly after the announcements shifted to the other list |
187 |
I unsubscribed to security as that was the only real reason I was |
188 |
reading it). |
189 |
|
190 |
- -- |
191 |
|
192 |
Susie |
193 |
arienadean@××××.ca |
194 |
http://arienadean.tripod.com/ |
195 |
|
196 |
Digitally signed |
197 |
GPG Key ID: E93F0D23 |
198 |
Key fingerprint = 33F8 0E9D 3AD1 23E0 C70F ECC6 7871 D811 E93F 0D23 |
199 |
|
200 |
- ----------------------------------------------------------------------- |
201 |
|
202 |
"We are not human beings having a spiritual experience. We are |
203 |
spiritual beings having a human experience." - Unknown |
204 |
|
205 |
|
206 |
|
207 |
-----BEGIN PGP SIGNATURE----- |
208 |
Version: GnuPG v1.2.1 (GNU/Linux) |
209 |
|
210 |
iD8DBQE+ruYieHHYEek/DSMRAq+4AJ9cC0Aq/OadlpwoLf+8sEy6sWUN6gCffHde |
211 |
skO4pH8xs/cs+rDEx90JTqU= |
212 |
=nZMw |
213 |
-----END PGP SIGNATURE----- |
214 |
|
215 |
-- |
216 |
gentoo-dev@g.o mailing list |