http://bugs.openembedded.org/show_bug.cgi?id=2913
Summary: add support for mercurial (hg) and bazaar-ng URLs
Product: BitBake
Version: 1.8.x
Platform: Other
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: BitBake
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
Currently bitbake is not able to parse and handle URLs for the distributed
version control systems mercurial and bazaar-ng.
Here is a quick guide for someone who wants to implement it:
mercurial: hg
-------------
* checkout: hg clone [-r REVISION] <URL> [DESTINATION]
* update: hg pull [-r REVISION]
This is the list of mercurial supported URLs:
http://[EMAIL PROTECTED]:port]/[path]
https://[EMAIL PROTECTED]:port]/[path]
ssh://[EMAIL PROTECTED]:port]/[path]
static-http://host[:port]/[path]
DESTINATION is an optional target directory which defaults to the current
working directory.
A revision can be specified in multiple ways:
"A plain integer is treated as a revision number. Negative
integers are treated as offsets from the tip, with -1 denoting the
tip.
A 40-digit hexadecimal string is treated as a unique revision
identifier.
A hexadecimal string less than 40 characters long is treated as a
unique revision identifier, and referred to as a short-form
identifier. A short-form identifier is only valid if it is the
prefix of one full-length identifier.
Any other string is treated as a tag name, which is a symbolic
name associated with a revision identifier. Tag names may not
contain the ":" character.
The reserved name "tip" is a special tag that always identifies
the most recent revision.
" (from man page)
See also the man page for hg: http://www.selenic.com/mercurial/hg.1.html
bazaar-ng: bzr
--------------
* checkout: bzr checkout --lightweight <SOURCEURL> [DESTINATION] [-r REVISION]
* update: bzr update [-r REVISION]
A SOURCEURL may have the following prefixes:
aftp://
bzr://
bzr+ssh://
ftp://
http://
https://
sftp://
[file://] (not needed for OE)
A revision may be the following:
revno:<INTEGER>
("revno:" is optional)
date:ISO-DATE
There are many other possibilities but those are not that interesting for OE's
purposes.
--
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Bitbake-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bitbake-dev
