Re: [textadept] Textadept Updater

From: Zhehao Mao <zhehao.....at.gmail.com>
Date: Thu, 03 Mar 2011 09:44:24 -0500

On 03/03/2011 09:10 AM, mitchell wrote:
> Hi,
>
> On Thu, 3 Mar 2011, Robert wrote:
>
>> On Thu, Mar 3, 2011 at 5:47 AM, Zhehao Mao <zhehao.....at.gmail.com> wrote:
>>> On 03/02/2011 09:43 PM, mitchell wrote:
>>>> Hi,
>>>>
>>>> On Wed, 2 Mar 2011, Zhehao Mao wrote:
>>>>
>>>>> I'm starting a new thread for this because I think it's kind of
>>>>> important. I've looked at the luarocks code, and it seems that all we
>>>>> have to do is change a bunch of filepaths in order to get it to
>>>>> install
>>>>> into the textadept directory instead of the luarocks directory. Do you
>>>>> guys think forking luarocks and customizing it for textadept is the
>>>>> way
>>>>> to go, or do you think we should just use the vanilla luarocks
>>>>> program?
>>>>
>>>> Ideally vanilla luarocks would be used. I don't want to distribute
>>>> luarocks with ta.
>>>>
>>>> mitchell
>>>>
>>> Ok, wait, so I've just though of another problem. If we use hg for the
>>> updater, wouldn't the C core have to recompiled on each update since the
>>> hg repo only includes the source files? Perhaps luarocks would be the
>>> better choice.
>
> There are already packages for previous releases so luarocks would be
> unnecessary. Hg is fine for tagging modules with releases.
>
>>>
>>> Howie
>>>
>>> --
>>
>> I thought you were asking about better ways to update language modules
>> and modules extending TA's functionality. Updating the application is
>> of course a different thing.
>>
>> Mitchell,
>> the plan is to distribute language models for "popular enough"
>> languages together with Textadept, correct?
>
> I don't really know what the plan is. I want all included modules to
> have adeptsenses if possible (and if reasonable); at least taking
> advantage of the documentation aspect if not autocompletion.
>
> mitchell
>
If it's only for the extension modules, using hg wouldn't be a problem.
We should probably keep a single "stable" repo that holds only modules
ready for release. That way, the updater doesn't have to worry about
getting previous revisions, it can just clone and pull at will.

Howie
Received on Thu 03 Mar 2011 - 09:44:24 EST

This archive was generated by hypermail 2.2.0 : Thu 08 Mar 2012 - 12:01:45 EST