public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How to publish an overlay
Date: Fri, 8 Feb 2013 14:10:34 +0200	[thread overview]
Message-ID: <CAHNvW1KyuPyo9WK5wWGX6D3KkieNVv8aDoQ6xRTyvUCGL5wgAA@mail.gmail.com> (raw)
In-Reply-To: <1360308525.3997.166.camel@big_daddy.dol-sen.ca>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

On Fri, Feb 8, 2013 at 9:28 AM, Brian Dolbec <dolsen@gentoo.org> wrote:

> On Fri, 2013-02-08 at 09:03 +0200, Kfir Lavi wrote:
> > Hi,
> > I'm the author of bashlibs - general library framework and libraries
> > for bash programing.
> > I have created new overlay for bash libraries.
> > https://github.com/kfirlavi/bashlibs/tree/master/gentoo/portage
> >
> > How do I publish it via layman or eix-remote?
> >
> > Regards,
> > Kfir
> >
> >
> Generally file a bug in bugzilla asking the overlay team to add it.
>
> Please supply all the info needed for creating the xml to add.  You
> could also pre-fill out the xml definition and attach it.  Don't forget
> to include all urls available, github can do git and http protocols.
>
> How people serve binaries (tar.gz source files) to complement the
repository?
Github doesn't seem to have a way to have a binary repository and serve
single files.
Heroku maybe?

Thanks,
Kfir


> See the layman's man page for instructions on creating an xml defintion.
>
> http://layman.sourceforge.net/#_overlay_list_format
>
>
>

[-- Attachment #2: Type: text/html, Size: 1837 bytes --]

  reply	other threads:[~2013-02-08 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08  7:03 [gentoo-dev] How to publish an overlay Kfir Lavi
2013-02-08  7:28 ` Brian Dolbec
2013-02-08 12:10   ` Kfir Lavi [this message]
2013-02-08 15:25     ` Rich Freeman
2013-02-08 19:08       ` Peter Stuge

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=CAHNvW1KyuPyo9WK5wWGX6D3KkieNVv8aDoQ6xRTyvUCGL5wgAA@mail.gmail.com \
    --to=lavi.kfir@gmail.com \
    --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: link
Be 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