From: "Jauhien Piatlicki" <piatlicki@gmail.com> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/g-sorcery:master commit in: / Date: Sat, 10 May 2014 02:03:47 +0000 (UTC) [thread overview] Message-ID: <1399687385.561e590173dbc44720c57df5c656a7e857a0f667.jauhien@gentoo> (raw) commit: 561e590173dbc44720c57df5c656a7e857a0f667 Author: Jauhien Piatlicki <jauhien <AT> gentoo <DOT> org> AuthorDate: Sat May 10 02:03:05 2014 +0000 Commit: Jauhien Piatlicki <piatlicki <AT> gmail <DOT> com> CommitDate: Sat May 10 02:03:05 2014 +0000 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/g-sorcery.git;a=commit;h=561e5901 update README --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 4b25590..f0070a8 100644 --- a/README.md +++ b/README.md @@ -46,16 +46,17 @@ databases with information about available software and so on. Installation and using ====================== -You should emerge **app-portage/layman-9999**. +You will need **app-portage/layman-9999** (when you emerge a backend you are +interested in it will be pulled in authomatically). Add `jauhien` overlay: **layman -a jauhien**. -Emerge g-sorcery: **emerge -va g-sorcery**. - Currently 2 backends are available: **gs-elpa** and **gs-pypi**. Here is an example of using gs-elpa backend. +Emerge backend you want to use: **emerge -va gs-elpa**. + There are two ways of using **gs-elpa**: * use it with **layman**
WARNING: multiple messages have this Message-ID (diff)
From: "Jauhien Piatlicki" <piatlicki@gmail.com> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/g-sorcery:dev commit in: / Date: Sat, 10 May 2014 02:03:18 +0000 (UTC) [thread overview] Message-ID: <1399687385.561e590173dbc44720c57df5c656a7e857a0f667.jauhien@gentoo> (raw) Message-ID: <20140510020318.MffMAKH1XnDYMZ5jaShwe7-AurQQHpxc0WDZ8yDreHw@z> (raw) commit: 561e590173dbc44720c57df5c656a7e857a0f667 Author: Jauhien Piatlicki <jauhien <AT> gentoo <DOT> org> AuthorDate: Sat May 10 02:03:05 2014 +0000 Commit: Jauhien Piatlicki <piatlicki <AT> gmail <DOT> com> CommitDate: Sat May 10 02:03:05 2014 +0000 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/g-sorcery.git;a=commit;h=561e5901 update README --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 4b25590..f0070a8 100644 --- a/README.md +++ b/README.md @@ -46,16 +46,17 @@ databases with information about available software and so on. Installation and using ====================== -You should emerge **app-portage/layman-9999**. +You will need **app-portage/layman-9999** (when you emerge a backend you are +interested in it will be pulled in authomatically). Add `jauhien` overlay: **layman -a jauhien**. -Emerge g-sorcery: **emerge -va g-sorcery**. - Currently 2 backends are available: **gs-elpa** and **gs-pypi**. Here is an example of using gs-elpa backend. +Emerge backend you want to use: **emerge -va gs-elpa**. + There are two ways of using **gs-elpa**: * use it with **layman**
next reply other threads:[~2014-05-10 2:03 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-10 2:03 Jauhien Piatlicki [this message] 2014-05-10 2:03 ` [gentoo-commits] proj/g-sorcery:dev commit in: / Jauhien Piatlicki -- strict thread matches above, loose matches on Subject: below -- 2015-09-13 19:32 Jauhien Piatlicki 2015-09-13 19:32 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki 2015-04-22 7:35 Jauhien Piatlicki 2015-04-20 21:36 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki 2015-04-22 7:35 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki 2014-09-29 19:38 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki 2014-09-29 19:39 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki 2014-05-10 2:03 Jauhien Piatlicki 2014-03-05 17:58 Jauhien Piatlicki 2013-11-22 17:08 Jauhien Piatlicki 2013-11-22 16:55 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki 2013-11-22 16:54 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki 2013-11-22 16:42 [gentoo-commits] proj/g-sorcery:dev " Jauhien Piatlicki 2013-11-22 16:42 ` [gentoo-commits] proj/g-sorcery:master " Jauhien Piatlicki 2013-11-22 16:38 Jauhien Piatlicki 2013-09-19 23:22 Jauhien Piatlicki 2013-09-19 23:21 Jauhien Piatlicki 2013-09-15 22:38 Jauhien Piatlicki 2013-09-15 14:32 Jauhien Piatlicki 2013-09-05 16:33 Jauhien Piatlicki 2013-08-30 17:00 Jauhien Piatlicki 2013-08-29 23:37 Jauhien Piatlicki 2013-08-29 21:30 Jauhien Piatlicki 2013-08-14 8:31 Jauhien Piatlicki 2013-08-12 0:42 Jauhien Piatlicki 2013-08-12 0:36 Jauhien Piatlicki 2013-08-06 20:16 Jauhien Piatlicki 2013-08-06 20:16 Jauhien Piatlicki 2013-08-05 0:54 Jauhien Piatlicki 2013-08-05 0:46 Jauhien Piatlicki 2013-07-30 19:02 Jauhien Piatlicki 2013-07-26 9:43 Jauhien Piatlicki 2013-07-22 17:10 Jauhien Piatlicki 2013-07-15 0:00 Jauhien Piatlicki 2013-07-14 23:51 Jauhien Piatlicki 2013-07-14 22:53 Jauhien Piatlicki 2013-07-14 1:00 Jauhien Piatlicki 2013-07-13 23:41 Jauhien Piatlicki 2013-07-11 0:09 Jauhien Piatlicki 2013-07-11 0:05 Jauhien Piatlicki 2013-07-02 14:50 Jauhien Piatlicki 2013-07-02 10:21 Jauhien Piatlicki 2013-06-30 19:55 Jauhien Piatlicki 2013-06-20 22:53 Jauhien Piatlicki 2013-06-20 22:53 Jauhien Piatlicki
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1399687385.561e590173dbc44720c57df5c656a7e857a0f667.jauhien@gentoo \ --to=piatlicki@gmail.com \ --cc=gentoo-commits@lists.gentoo.org \ --cc=gentoo-dev@lists.gentoo.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox