On Sunday 30 May 2004 06:32 pm, Kim Woelders wrote:
Now available: http://sourceforge.net/project/showfiles.php?group_id=2
if you dont mind me asking, whats up with the extra version tag on
the tarball ? why is enlightenment-0.16.7-pre1 named
enlightenment-0.16.7-0.56.tar.gz and not
enlightenment-0.16.7_pre1.tar.gz ? why isnt enlightenment-0.16.7-0.60.tar.gz named
enlightenment-0.16.7_pre2.tar.gz ? why isnt
enlightenment-0.16.7-0.65.tar.gz named enlightenment-0.16.7_pre3.tar.gz ? and so on and so forth with the
other sub packages -mike
It is what makes most sense to me. During the 16.6 pre's I built the gz and rpm packages and renamed them to _preX. The RPM's contain their original name, so some rpm archives renamed them back into that. You can still find enlightenment-0.16.6-0.38rh9.i386.rpm, and I have no idea which pre that was.
So, this time I didn't want to rename the RPM's. I could then change the RPM "Release" to preX before building, but then why not just use the Release number that is there anyway?
Now only the .gz's are renamed, and why not let them match the RPM names?
If there is a better way of doing things this might be a good time to sort it out so that it can be done right next time.
/Kim
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
enlightenment-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
