Page 1 of 1
How does "hg" work?
Posted: 08 Sep 2010, 15:06
by dedanna1029
Hadn't ever had to use it, but I'd like to see if
Pino has OAuth support yet for Twitter.
I tried the code at the top of the page at the link I just posted, and it doesn't work:
Code: Select all
# hg clone https://pino-twitter.googlecode.com/hg/ pino-twitter
bash: hg: command not foundWhat do I need to install, or am I doing the wrong thing altogether?
Thanks!
Re: How does "hg" work?
Posted: 08 Sep 2010, 21:41
by viking60
hg is a control system like git.
Yaourt -S pino-twitter-hg
Pizzapunk has put it in AUR
(And it is not working) Because it is not the latest version:)
You will need to use PKGBUILD. And you can use the scripts already there in AUR.
Re: How does "hg" work?
Posted: 09 Sep 2010, 03:28
by dedanna1029
What about for Fedora? I already have the version from yaourt installed.
Was trying to use the "hg" code in Fedora; I want to try the latest they have in there.
Re: How does "hg" work?
Posted: 09 Sep 2010, 15:33
by viking60
RTFM
Code: Select all
:) hg clone
hg clone: invalid arguments
hg clone [OPTION]... SOURCE [DEST]
make a copy of an existing repository
Create a copy of an existing repository in a new directory.
If no destination directory name is specified, it defaults to the basename
of the source.
The location of the source is added to the new repository's .hg/hgrc file,
as the default to be used for future pulls.
See "hg help urls" for valid source format details.
It is possible to specify an "ssh://" URL as the destination, but no
.hg/hgrc and working directory will be created on the remote side. Please
see "hg help urls" for important details about "ssh://" URLs.
A set of changesets (tags, or branch names) to pull may be specified by
listing each changeset (tag, or branch name) with -r/--rev. If -r/--rev is
used, the cloned repository will contain only a subset of the changesets
of the source repository. Only the set of changesets defined by all
-r/--rev options (including all their ancestors) will be pulled into the
destination repository. No subsequent changesets (including subsequent
tags) will be present in the destination.
Using -r/--rev (or 'clone src#rev dest') implies --pull, even for local
source repositories.
For efficiency, hardlinks are used for cloning whenever the source and
destination are on the same filesystem (note this applies only to the
repository data, not to the working directory). Some filesystems, such as
AFS, implement hardlinking incorrectly, but do not report errors. In these
cases, use the --pull option to avoid hardlinking.
In some cases, you can clone repositories and the working directory using
full hardlinks with
$ cp -al REPO REPOCLONE
This is the fastest way to clone, but it is not always safe. The operation
is not atomic (making sure REPO is not modified during the operation is up
to you) and you have to make sure your editor breaks hardlinks (Emacs and
most Linux Kernel tools do so). Also, this is not compatible with certain
extensions that place their metadata under the .hg directory, such as mq.
Mercurial will update the working directory to the first applicable
revision from this list:
a) null if -U or the source repository has no changesets
b) if -u . and the source repository is local, the first parent of the
source repository's working directory
c) the changeset specified with -u (if a branch name, this means the
latest head of that branch)
d) the changeset specified with -r
e) the tipmost head specified with -b
f) the tipmost head specified with the url#branch source syntax
g) the tipmost head of the default branch
h) tip
Returns 0 on success.
options:
-U --noupdate the clone will include an empty working copy (only a
repository)
-u --updaterev REV revision, tag or branch to check out
-r --rev REV [+] include the specified changeset
-b --branch BRANCH [+] clone only the specified branch
--pull use pull protocol to copy metadata
--uncompressed use uncompressed transfer (fast over LAN)
-e --ssh CMD specify ssh command to use
--remotecmd CMD specify hg command to run on the remote side
[+] marked option can be specified multiple times
use "hg -v help clone" to show global options
Re: How does "hg" work?
Posted: 09 Sep 2010, 15:57
by dedanna1029
That's my point. I don't have a manual to read. What do I need to install? mercurial (hgsvn)? What?
Code: Select all
$ hg clone
bash: hg: command not foundI've tried as su too, and got the same thing.
Re: How does "hg" work?
Posted: 09 Sep 2010, 16:50
by viking60
Re: How does "hg" work?
Posted: 09 Sep 2010, 18:20
by dedanna1029
Okay, thanks. Installed it from the repos. Will try it later. Watching an almost 3-hr video now (see "What are you watching right now?" thread).
Re: How does "hg" work?
Posted: 15 Sep 2010, 01:29
by dedanna1029
I don't get what this is supposed to "do".
Pino 3 has just barely been released (is not alpha yet though):
Code: Select all
$ hg clone http://bitbucket.org/troorl/pino3
destination directory: pino3
requesting all changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 91 changes to 86 files
updating to branch default
86 files updated, 0 files merged, 0 files removed, 0 files unresolvedI try starting Pino though, and it's the same ol' version I already had. Something's not clicking about this.
Code: Select all
$ whereis pino
pino: /usr/bin/pino /usr/share/pinoThanks.
Re: How does "hg" work?
Posted: 15 Sep 2010, 11:41
by viking60
I had the same problem no new version.
It would be an option to give up that hopeless twitter stuff?
(Rhetorical question - your answer is
)
Re: How does "hg" work?
Posted: 15 Sep 2010, 16:02
by dedanna1029
Maybe. Haven't posted jack in some 3 days now but maybe a couple posts.