mirror of
https://github.com/gentoo-mirror/gentoo.git
synced 2026-02-09 01:27:34 -08:00
56bd759df1
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
26 lines
1.2 KiB
XML
26 lines
1.2 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
|
|
<pkgmetadata>
|
|
<herd>python</herd>
|
|
<longdescription>
|
|
This is a ground-up rewrite of Perspective Broker, which itself is Twisted's
|
|
native RPC/RMI protocol (Remote Procedure Call / Remote Method Invocation).
|
|
If you have control of both ends of the wire, and are thus not constrained to
|
|
use some other protocol like HTTP/XMLRPC/CORBA/etc, you might consider using
|
|
Foolscap.
|
|
|
|
Fundamentally, Foolscap allows you to make a python object in one process
|
|
available to code in other processes, which means you can invoke its methods
|
|
remotely. This includes a data serialization layer to convey the object
|
|
graphs for the arguments and the eventual response, and an object reference
|
|
system to keep track of which objects you are connecting to. It uses a
|
|
capability-based security model, such that once you create a non-public
|
|
object, it is only accessible to clients to whom you've given the
|
|
(unguessable) FURL. You can of course publish world-visible objects that
|
|
have well-known FURLs.
|
|
</longdescription>
|
|
<upstream>
|
|
<remote-id type="pypi">foolscap</remote-id>
|
|
</upstream>
|
|
</pkgmetadata>
|