Comment 21 for bug 1319545

1) I'm not sure what would be needed to get feeds over to the new world. I presume it just means, we need a console script?

2) Ok.

3) Let's make life easier for this ticket and say that upgrading libmemcached is *not* part of karlserveless. It is ok for now if you are able to build it but he isn't.

--Paul

On Sep 25, 2014, at 11:12 AM, Chris Rossi <email address hidden> wrote:

> I've gone ahead and rebased on top of current master the karlserveless
> branches for both the development buildout and the karl package.
> Existing checkouts of these packages should be deleted/recloned.
>
>> From reading the comments, the things I'm concerned about and will
> investigate:
>
> 1) Figure out what's going on with feeds now. Do they need to be
> reconfigured for OSI?
>
> 2) Dump any persistent settings for OSF and make sure the wind up in
> karl.ini.
>
> 3) I think mcdonc's memcached woes are just on his box, but I'll make
> sure we can use memcache din the gocept environment. There is also
> another ticket related to seeing if we can just use a system
> libmemcached in osideploy.
>
> --
> You received this bug notification because you are subscribed to KARL3.
> https://bugs.launchpad.net/bugs/1319545
>
> Title:
> Investigate removing karlserve
>
> Status in KARL3:
> In Progress
>
> Bug description:
> Absent the never-realized "plankton KARL" business model, the
> complexity / obfuscation of karlserve is outweighing its utility. We
> need to figure out how much work is involved to rip it out.
>
> As a deliverable, create a branch of the 'dev-buildout' and remove all
> traces of 'karlserve' from it. Document what features will need to be
> re-worked (e.g., plugin scripts, etc.)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/1319545/+subscriptions