Bug 153174 - emerging "emacs-cvs-22.0.50-r?" fails, because HEAD is 22.0.90
|
Bug#:
153174
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: emacs@gentoo.org
|
Reported By: XL@XLsigned.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: emerging "emacs-cvs-22.0.50-r?" fails, because HEAD is 22.0.90
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-10-28 13:04 0000
|
Note: The build fails during "(dyn_)install" and not during upstream's build
procedure.
I'll attach my "emacs-cvs-22.0.90.ebuild" which is simply a copy of the
"22.0.50-r3" ebuild with SLOT set to "22.0.90".
(... and an emacs-22.0.90.desktop file)
Furthermore I'm a little confused that "emacs-cvs" is build in
"/var/tmp/portage/app-editors/..." (and is then deleted entirely)
Or is this "by design" for cvs builds?
Axel
(In reply to comment #0)
> Furthermore I'm a little confused that "emacs-cvs" is build in
> "/var/tmp/portage/app-editors/..." (and is then deleted entirely)
Uhm? Everything is being built in PORTAGE_TMPDIR (and deleted after merge)
... obviously the behaviour has been changed in recent versions of portage
The build directory used to be for example
${PORTAGE_TMPDIR}/portage/vim-6.3-r4
and has not been deleted entirely after finishing the build,
i. e. the "temp" folder remained.
Whereas now the build directory is
${PORTAGE_TMPDIR}/portage/app-editors/vim-7.0.17
and is entirely removed after finishing the build.
So, I will delete a lot of (obsolete) folders after
"emerge --update --newuse world" has completed. :-)
The "emacs-cvs" issue should be addressed anyway, i. e.
independent of this (interesting) off-topic discussion.
:-) Axel
Changed it so that the .desktop file is generated.
Thanks, this was petty fast!