RFC: bootstrapping Forge packages

[Mike Miller]

On Thu, Feb 28, 2013 at 7:44 AM, Juan Pablo Carbajal wrote:
> On Thu, Feb 28, 2013 at 1:38 PM, Carnë Draug <address@hidden> wrote:
>> On 28 February 2013 12:18, Juan Pablo Carbajal <address@hidden> wrote:
>>> I noticed that the package needs to be boostraped before it can be
>>> distributed. This breaks the current version of releasePKG.
>>> @Carnë: What would be the procedure with packages like this?
>>
>> The procedure to release package like this is that the package manager
>> runs ./bootstrap first, and then create a tarball of the result. Also,
>> remove the "autom4te.cache" directory that may have been generated.
>> Whether to also remove the bootstrap and configure.ac/in files from
>> the tarball, is up to the package manager (probably we should settle
>> on something?).
>>
>> Carnë
>
> ok, I am modifying releasePKG to run bootstrap and remove the
> "autom4te.cache" directory. The other files may help to debug user
> problems

Among the "main" packages there are 3 with a bootstrap script and 15
with an autogen.sh script.

Since releasePKG now automatically handles bootstrap should we be
encouraging standardization on that name? Or should releasePKG support
both?

-- 
mike