On Fri, 12 Mar 2004 07:56:37 -0500 Kyle Gonzales <[EMAIL PROTECTED]> babbled:

> So, I've been playing around with Enlightenement DR17 in its various 
> releases for almost 2 years now.  I can download CVS, I can make sure 
> the software builds, even made RPMs for the low end libraries (trying to 
> make enough RPMs to allow someone to use Entice, eRSS, etc. without 
> having to pull CVS).  Go me.

yay! we need packagers any time - though the real time they are needed is near
"release" :)

> The problem is, I don't feel like I'm really contributing to the 
> project.  I am not proficient enough with C or C++ to really contribute 
> code, tho I know enough to read tips from google, hack around makefiles, 

although thats our major need at the moment :(

> etc.  One day, when I have time, I really want to be able to contribute 
> that way, but I can't right now.
> 
> So, in the meantime...  what can I do to help?  Is code testing an 
> option?  If there were a list of things along the lines of "hey we have 
> new code, try this, this and this, and see if it breaks.  if it does, 
> give us tracebacks" it would be helpful.  The Pan newsreader did this 
> awhile back, and I was able to beat it senseless for about a week, 
> causing at least one release myself due to bugs I tracked down. :)

hmm - we need people to maybe trawl the cvs commits list very regularly and turn
coding into news articles and publicity. also comments on irc as well where
ad-hoc discussion happens. (though this needs filtering as sometimes its just
plain mindless bitching :) ). we have some people doing some of this but this is
ALWAYS "the more the better" kind of work :)

if this means writing articles for slashdot, newsforge, osnews or any other
suitable online publication - thats all good! :) 

> I use Red Hat/Fedora based systems, currently RH9, moving to Fedora Core 
> 2 once it is released next month.  Once I move in a couple months, I 
> will have my computer lab again, and can test on other distros (or even 
> other versions of Unix/BSD/etc, like FreeBSD or whatever).
> 
> Also, does anyone have a system setup or can point me to a place to find 
> out how to make RPMs of CVS snapshots easily?  I would be glad to set 
> this up and maintain this, if only I had a good idea of how to start. 
> Manually changing the spec files, tarring up new CVS directories, its 
> not fun.

me: i make sure the .spec files in the cvs tree is correct, make sure its
inclueded in the EXTRA_DIST of the Makefile.am then:

make distcheck
this will produce project-1.0.0.tar.gz or such a tarball - now
sudo rpm -ta project-1.0.0.tar.gz

and you SHOULD be fine... unless the .spec file is screwed or the build
procedure is... :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [EMAIL PROTECTED]
熊耳 - 車君 (数田)                  [EMAIL PROTECTED]
Tokyo, Japan (東京 日本)


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
enlightenment-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to