why are we calling it kde3mod? that is pointless.

We are rebranding kde3 to Trinity. I don't think we should keep it the
same. that causes confusion.

I have started moving the PKGBUILDs to the AUR, which is fine. (the
independant ones not the entire tree) I can maintain them (seeing as
they do not change often, they are SVN builds.)

I think we need to just wait until 3.5.13 is out completely then
switch over. Its only a few months till then and there is much work
that needs to be done on 3.5.12.

Calvin

On 22 February 2011 12:47, David C. Rankin
<drankinatty@...> wrote:
> On 02/22/2011 11:32 AM, calvin morrison wrote:
>> I am very glad Trinity has a few Arch Linux users and devels
>> (including myself) hopefully we can find great support from the
>> community. I would love to see Trinity in [community]. anyone know a
>> TU from arch we could convince?
>>
>> Calvin Morrison
>
> Not right off hand, but so far the reception to the Trinity on Arch project has
> been favorable. With Albert's update to kdemod3 and the svn PKGBUILDs working
> for everything ported to CMake, I think we have a rational update path to propose.
>
> I'll check out the kdemod3 3.5.12 packages today. If all is good, then I think a
> rational proposal would be:
>
> (1) Move kdemod3 3.5.12 to community or AUR;
> (2) Have a maintainer for kdemod3 3.5.12 tweaks and fixes while 3.5.13 finishes
> the transition to CMake
> (3) Replace kdemod3 with Trinity 3.5.13 when released.
>
> I think we can run this by Allan and the other powers that be on the arch list
> after we a confident in kdemod3 3.5.12.
>
> Any other thoughts?
>
> --
> David C. Rankin, J.D.,P.E.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
>