[gentoo-user] configure.ac and Makefile.am easy_view ?

[gentoo-user] configure.ac and Makefile.am easy_view ?

[James]

Hello,

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 ? If not, then when I build a given package, is there
something like elogviewer that can be customized to look at these 2 files?
I do I keeps those files around for a while in some sort of semi-automated
systematic way?


Maybe use Eclipse or some other lighter_weight gui tool?

Tips and comments are most welcome.


James

[gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[James]

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 inspect and ponder these files: configure.ac
and Makefile.am for a given ebuild. Is there an easy way to look at them
*without*  compiling the ebuild ? 

James

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Michael Orlitzky]

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 inspect and ponder these files: configure.ac
> and Makefile.am for a given ebuild. Is there an easy way to look at them
> *without*  compiling the ebuild ? 
> 

Those files are part of the upstream tarball. The easiest way to fetch
the sources without compiling them is with `emerge -f`. Then you can
copy the tarball out of $DISTDIR and unpack it somewhere.

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 sources under /var/tmp/portage.

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Jc García]

2015-03-28 8:36 GMT-06:00 James <wireless@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 /var/tmp/portage/cat/pkg/work/ for the 'prepared'
sources.

(As root or as the portage user)

# ebuild $PORTDIR/cat/pkg/pkg-00.ebuild prepare

I have this alias in my bashrc for using the ebuild command easily.

alias=" sudo -u portage ebuild "

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Jc García]

2015-03-28 11:08 GMT-06:00 Jc García <jyo.garcia@gmail.com>:
>
> I have this alias in my bashrc for using the ebuild command easily.
>
*Correction
 alias ebuild=" sudo -u portage ebuild "

[gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[James]

Michael Orlitzky <mjo <at> gentoo.org> writes:


> Those files are part of the upstream tarball. The easiest way to fetch
> the sources without compiling them is with `emerge -f`. Then you can
> copy the tarball out of $DISTDIR and unpack it somewhere.

> 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 sources under /var/tmp/portage.

Hmm... That's kinda what I've been doing. I want a way to save those
files, once I tag a given ebuild for this sort of curious  and closer
examination. GLEP_64 would go a long way to automating this, with
a DAG. I just wanted to make sure there was not an existing or easier
way to do this, that I had not considered.


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 more suited tool for extending the
existing functionality to view key files of an ebuild?

Other ideas?


James

[gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[James]

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 'prepared'
> sources.

> # ebuild $PORTDIR/cat/pkg/pkg-00.ebuild prepare

Ok I'll give this a whirl.


> I have this alias in my bashrc for using the ebuild command easily.
> alias=" sudo -u portage ebuild "


Correction
 alias ebuild=" sudo -u portage ebuild "

Ahhh. OK this make it so that proper file ownership is always correct?


But, does this ever interfere with any of the other portage syntax?
i.e. do I every need to unset this expanded syntax for other ebuild
functions? Quick glance at the man pages I do not see any reason
to not use the expansion universally.....


James

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Jc García]

2015-03-28 11:26 GMT-06:00 James <wireless@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 'prepared'
>> sources.
>
>> # ebuild $PORTDIR/cat/pkg/pkg-00.ebuild prepare
>
> Ok I'll give this a whirl.
>
>
>> I have this alias in my bashrc for using the ebuild command easily.
>> alias=" sudo -u portage ebuild "
>
>
> Correction
>  alias ebuild=" sudo -u portage ebuild "
>
> Ahhh. OK this make it so that proper file ownership is always correct?
>
It is just to not use root, and because the portage user has write
privileges in /var/tmp/portage/

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Todd Goodman]

* Michael Orlitzky <mjo@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 the ebuild ? 
> > 
> > oops,
> > 
> > Should be : 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
> > *without*  compiling the ebuild ? 
> > 
> 
> Those files are part of the upstream tarball. The easiest way to fetch
> the sources without compiling them is with `emerge -f`. Then you can
> copy the tarball out of $DISTDIR and unpack it somewhere.
> 
> 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 sources under /var/tmp/portage.
> 

Wouldn't 'ebuild <ebuild_file_name> prepare' do what you want without
trying to time a Ctrl-C?

[gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[James]

Todd Goodman <tsg <at> bonedaddy.net> writes:


> * Michael Orlitzky <mjo <at> 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 without 
> > >> compiling the ebuild ? 


> > Those files are part of the upstream tarball. The easiest way to fetch
> > the sources without compiling them is with `emerge -f`. Then you can
> > copy the tarball out of $DISTDIR and unpack it somewhere.

> > 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 sources under /var/tmp/portage.

> Wouldn't 'ebuild <ebuild_file_name> prepare' do what you want without
> trying to time a Ctrl-C?


The man page says: Prepares  the extracted sources by running the
src_prepare() function specified in the ebuild file. When src_prepare()
starts, the  current working  directory  will  be  set to ${S}.

I work with /usr/local/portage/* on a variety of new ebuilds and other
hacks. Sometime these  files under /var/tmp/portage are persistent and
sometimes they are not. I'm not sure where you set the rules (configs?)
to keep various files around a while after cleaning up. Surely I've
experimented with the ebuilds of new codes I'm putting together, so
I look for guidance and a semantic that other, more experienced folks use
with ebuilds. I just compiled seamonkey last night (Installed versions: 
2.33.1(12:56:48 AM 03/28/2015) and it is not there, but I also installed
firefox and it is there in (var/tmp/portage/www-client/firefox-24.5.0/)

 so # find . -print | grep -i '.*[.]ac'

./work/mozilla-esr24/toolkit/crashreporter/google-breakpad/configure.ac
./work/mozilla-esr24/toolkit/crashreporter/google-breakpad/src/
third_party/glog/configure.ac
./work/mozilla-esr24/js/src/ctypes/libffi/configure.ac
./work/mozilla-esr24/memory/jemalloc/src/configure.ac
./work/mozilla-esr24/gfx/harfbuzz/configure.ac
./work/mozilla-esr24/modules/freetype2/builds/unix/configure.ac
./work/mozilla-esr24/media/webrtc/trunk/testing/gtest/configure.ac

and  # find . -print | grep -i 'Makefile.am'

./net-analyzer/iftop-1.0_pre4/work/iftop-1.0pre4/Makefile.am
./net-analyzer/iftop-1.0_pre4/work/iftop-1.0pre4/config/Makefile.am
./x11-misc/pcmanfm-0.9.10/work/pcmanfm-0.9.10/Makefile.am
./x11-misc/pcmanfm-0.9.10/work/pcmanfm-0.9.10/data/Makefile.am
<snip>

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 in the portage tree. Some are there, some remain
and others.... who knows.

So with this in mind, how do I "tag" certain ebuilds to at least save the
configure.ac and Makefile.am files only for selected ebuild; either of which
may be in /usr/portage or /usr/local/portage?  (sorry for not being more
clear). Is this just some inconsistency in how various ebuilds are constructed?

Ideas and comments are most welcome.

James

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Jc García]

2015-03-28 14:43 GMT-06:00 James <wireless@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 in the portage tree. Some are there, some remain
> and others.... who knows.
>
This depends on wheter the ebuild was succesfully built, if so:

 ebuild ${ebuild_path} clean
is called and all the files under /var/tmp/portage/cat/pkg are removed

When I'm trying to make an ebuild I only use the ebuild(5) tool, for
building,  and call manually up to where I want to build(prepare,
configure, compile, etc...) and only when

ebuild ${ebuild_path} package

Has completed successfully, I use emerge so I don't get unwanted cleanups.

> So with this in mind, how do I "tag" certain ebuilds to at least save the
> configure.ac and Makefile.am files only for selected ebuild; either of which
> may be in /usr/portage or /usr/local/portage?  (sorry for not being more
> clear). Is this just some inconsistency in how various ebuilds are constructed?
>
I don't see the utility of having these files apart form it's source
tree, if you modified them, then make patches, I usually unpack the
sources to a directory under $HOME, or clone the upstream repo, try to
get a working build as my user(I build experimental stuff with
--prefix="$HOME/opt/" so my system stays clean). Make a patch of my
changes if any, and then try to introduce the patch into an ebuild.

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Jc García]

2015-03-28 15:26 GMT-06:00 Jc García <jyo.garcia@gmail.com>:
> When I'm trying to make an ebuild I only use the ebuild(5) tool,
It was the ebuild(1) tool.

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Michael Orlitzky]

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 more suited tool for extending the
> existing functionality to view key files of an ebuild?

FEATURES="noclean" will leave the entire built source tree intact. It
will waste a bunch of space but you'll have a copy of the files you want.

The package manager is what normally deletes those files, so if you
wanted to file a feature request somewhere, it would have to be with
portage. IMO I think they'll say no, but you could request something
like a CLEAN_MASK variable that allows you to prevent certain files from
being cleaned.

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Michael Orlitzky]

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 sources under /var/tmp/portage.
>>
> 
> Wouldn't 'ebuild <ebuild_file_name> prepare' do what you want without
> trying to time a Ctrl-C?
> 

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 =)

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Franz Fellner]

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
> >> compiling. Then you can find the sources under /var/tmp/portage.
> >>
> > 
> > Wouldn't 'ebuild <ebuild_file_name> prepare' do what you want without
> > trying to time a Ctrl-C?
> > 
> 
> 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 least for me ;)), you don't need to be inside
the directory where the ebuild lives.
And to get the unpatched src tree simply use "ebuild <EBUILD> unpack". After that you
can run "ebuild <EBUILD> prepare" to prepare (e.g. patch) the sources. That's way easier to get
a well defined result than hitting C-c :)

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Michael Orlitzky]

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 least for me ;)), you don't need to be inside
> the directory where the ebuild lives.

Well, yeah, but you have to give it the full path then:

$ ebuild
/var/cache/portage/repositories/gentoo/sys-process/xjobs/xjobs-20140125.ebuild
prepare

$ emerge xjobs
^C

Ain't nobody got time for that =)

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Peter Humphrey]

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 earlier =)
> > 
> > The ebuild-command works from every directory (at least for me ;)), you
> > don't need to be inside the directory where the ebuild lives.
> 
> Well, yeah, but you have to give it the full path then:
> 
> $ ebuild
> /var/cache/portage/repositories/gentoo/sys-process/xjobs/xjobs-20140125.eb
> uild prepare
> 
> $ emerge xjobs
> ^C
> 
> Ain't nobody got time for that =)

$ ebuild $(equery w xjobs) prepare

-- 
Rgds
Peter.

[gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[James]

Peter Humphrey <peter <at> prh.myzen.co.uk> writes:


> > $ emerge xjobs
> > ^C

> > Ain't nobody got time for that =)

> $ ebuild $(equery w xjobs) prepare


Hey guys,

Thanks for the discussion.
I'm going to ponder these comments and test/verify suggestions a bit and
develop my semantic for this.



Thx, 

James

Re: [gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[Michael Orlitzky]

On 03/29/2015 05:46 AM, Peter Humphrey wrote:
> 
> $ ebuild $(equery w xjobs) prepare
> 

Ok, you got me!