On 03/29/2015 05:46 AM, Peter Humphrey wrote:
$ ebuild $(equery w xjobs) prepare
Ok, you got me!
Michael Orlitzky wrote:
On 03/28/2015 01:40 PM, Todd Goodman wrote:
Some ebuilds may patch configure.ac or Makefile.am -- in that case it's
a little harder. I'm sure there's an elegant way to do it, but what I
usually do is begin to emerge the package and Ctrl-C it when it starts
On Sunday 29 March 2015 02:24:00 Michael Orlitzky wrote:
On 03/29/2015 02:06 AM, Franz Fellner wrote:
Yeah, but I have to be in the directory where the ebuild lives for that
to work. `emerge foo` works anywhere. It's also more flexible -- if I
want the *unpatched* files, I just Ctrl-C
On 03/29/2015 02:06 AM, Franz Fellner wrote:
Yeah, but I have to be in the directory where the ebuild lives for that
to work. `emerge foo` works anywhere. It's also more flexible -- if I
want the *unpatched* files, I just Ctrl-C earlier =)
The ebuild-command works from every directory (at
2015-03-28 14:43 GMT-06:00 James wirel...@tampabay.rr.com:
likewise I've been hacking at ebuilds for apache (spark and mesos)
The spark file are still under /var/tmp/portage/sys-cluster but the mesos
files, compiled just yesterday are not under /var/tmp/portage. The
same is true for ebuild
On 03/28/2015 01:17 PM, James wrote:
Is there a way to includes those files for archiving so something like
elogviewer could make them available systematically? Do you think the
maintainer of elogviewer is open to that sort of request, formally (BGO) or
informally (personal email?). Another
On 03/28/2015 01:40 PM, Todd Goodman wrote:
Some ebuilds may patch configure.ac or Makefile.am -- in that case it's
a little harder. I'm sure there's an elegant way to do it, but what I
usually do is begin to emerge the package and Ctrl-C it when it starts
compiling. Then you can find the
2015-03-28 15:26 GMT-06:00 Jc García jyo.gar...@gmail.com:
When I'm trying to make an ebuild I only use the ebuild(5) tool,
It was the ebuild(1) tool.
2015-03-28 8:36 GMT-06:00 James wirel...@tampabay.rr.com:
Is there an easy way to look at them
*without* compiling the ebuild ?
I use /usr/bin/ebuild for this, emege run this when building, just
run the build up to the prepare function so patches are applied if
any, and look in
2015-03-28 11:08 GMT-06:00 Jc García jyo.gar...@gmail.com:
I have this alias in my bashrc for using the ebuild command easily.
*Correction
alias ebuild= sudo -u portage ebuild
On 03/28/2015 10:36 AM, James wrote:
James wireless at tampabay.rr.com writes:
Often, I need to inspect and ponder these files: configure.ac and Makefile
.am for a given ebuild. Is there an easy way to look at them with
compiling the ebuild ?
oops,
Should be : Often, I need to
2015-03-28 11:26 GMT-06:00 James wirel...@tampabay.rr.com:
Jc García jyo.garcia at gmail.com writes:
I use /usr/bin/ebuild for this, emege run this when building, just
run the build up to the prepare function so patches are applied if
any, and look in /var/tmp/portage/cat/pkg/work/ for the
* Michael Orlitzky m...@gentoo.org [150328 12:11]:
On 03/28/2015 10:36 AM, James wrote:
James wireless at tampabay.rr.com writes:
Often, I need to inspect and ponder these files: configure.ac and Makefile
.am for a given ebuild. Is there an easy way to look at them with
compiling
13 matches
Mail list logo
