From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] xattr wrapper for install, bug #465000
Date: Thu, 30 Jan 2014 20:53:48 -0800 [thread overview]
Message-ID: <20140130205348.517bf35c@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <7032574.jMnViApMpc@vapier>
On Thu, 30 Jan 2014 23:43:53 -0500
Mike Frysinger <vapier@gentoo.org> wrote:
> On Sunday, January 26, 2014 17:53:44 Anthony G. Basile wrote:
> > 1) I'm not 100% sure how to do that.
>
> we'll have to (re-)introduce support for building C files. shouldn't
> be too hard to start a new directory to hold all the C code. and a
> simple Makefile to build them all. i think the tbz2tool.c was the
> only C program we had before and it was compiled via the ebuild
> (which we should avoid).
>
> > 2) We may want to install it at /usr/bin/install-xattr
> > because I'm sure it will be useful for more than just portage.
>
> if that's the case, then i don't think it belongs in portage. make
> it a sep package that portage will just depend on.
> -mike
Yes, I agree, make it a separate pkg. That way it is useful for other
pkgs and utilities. I am doing the same for several other small
utility libs to avoid copy/pasting the same code over and over again.
Besides, portage will have the python code as an emergency backup.
--
Brian Dolbec <dolsen>
next prev parent reply other threads:[~2014-01-31 4:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 22:53 [gentoo-portage-dev] xattr wrapper for install, bug #465000 Anthony G. Basile
2014-01-27 14:02 ` vivo75
2014-01-28 4:36 ` Mike Frysinger
2014-01-29 16:33 ` Anthony G. Basile
2014-01-29 23:50 ` Francesco R.
2014-01-31 4:43 ` Mike Frysinger
2014-01-31 4:53 ` Brian Dolbec [this message]
2014-01-31 19:55 ` Greg Turner
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=20140130205348.517bf35c@big_daddy.dol-sen.ca \
--to=dolsen@gentoo.org \
--cc=gentoo-portage-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