Subrata Modak wrote:
> Hi Mike,
>
> On Thu, 2008-12-11 at 05:11 -0500, Mike Frysinger wrote:
>> On Thursday 11 December 2008 04:28:34 Subrata Modak wrote:
>>> On Fri, 2008-12-05 at 12:36 -0500, Mike Frysinger wrote:
>>>> On Friday 05 December 2008 10:41:45 Dmitry Guryanov wrote:
>>>>> On Friday 05 December 2008 02:12:52 pm Pradeep K Surisetty wrote:
>>>>>> i run autoconf. Build fails here too. It requires higher
>>>>>> version of autoconf (2.61 or higher).
>>>>>> Please find the below logs.
>>>>>>
>>>>>>
>>>>>> <machine> ltp-full-20081130]# make autoconf
>>>>>> autoconf
>>>>>> configure.ac:1: error: Autoconf version 2.61 or higher is required
>>>>>> configure.ac:1: the top level
>>>>>> autom4te: /usr/bin/m4 failed with exit status: 63
>>>>>> make: *** [configure] Error 63
>>>>> I think it will be good to publish ltp releases with created
>>>>> ./configure script, Because not all distributions has autoconf>=.61
>>>>> and not all users knows how to use it.
>>>> it should be. i dont know how Subrata makes releases, but i'm guessing
>>>> we should add a "dist" target so all these little gotchas can be
>>>> prevented.
>>> Please go ahead and add it/them to the CVS.
>> could you describe how you currently make a release tarball ?
>
> I just follow a documentation procedure my predecessors´ followed at IBM
> and left for me. I can summarise them as:
>
> External Process:
> * Build Release
> * Document all major changes since previous release in
> ChangeLog:
> 1. Run: #cvs log -d "MM/DD/YY<MM/DD/YY"> cvslog
> * The first MM/DD/YY should be the date of
> the previous release, and the second
> MM/DD/YY should be the current release
> date. Use the file, "output", to
> retrieve the ChangeLog information.
> 2. You must now update the ChangeLog file using the
> information contained in the changelog file.
> * Commit the ChangeLog file to the CVS tree: #cvs commit
> ChangeLog
> * Create the LTP release package: #cvs export -D "MONTH
> DAY, YEAR HH:MMam/pm" ltp
> * This will pull down the latest LTP without the
> CVS directories. Make sure to use the current
> date and time.
> * Check the ChangeLog file to make sure your
> updates are there.
> * Remove the "scratch" directory and any tests still in
> development.
I am a little confused about the audit-tests directory. It seems to be present
in -full releases since september, but not in CVS nor in any -intermediate
release. What is the cause here?
Regards
Jiri Palecek
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
