This is a 32-bit Doomsday 1.9.0-beta4 binary package. It's purpose is for 64-bit gentoo users (with multilib) that don't want to keep waiting around for doomsday to compile correctly on 64bit. Reproducible: Always Steps to Reproduce:
Created attachment 120487 [details] doomsday-bin-1.9.0_beta4.ebuild you'll have to download the binary package manually. I got mine from http://dotpups.de/dotpups/Games/Doomsday/deng-1.9.0-beta4/deng-1.9.0-beta4.tgz rename it to deng-bin-1.9.0-beta4.tgz, and stick it in /usr/portage/distfiles
(In reply to comment #1) > Created an attachment (id=120487) [edit] > doomsday-bin-1.9.0_beta4.ebuild > > you'll have to download the binary package manually. I got mine from > http://dotpups.de/dotpups/Games/Doomsday/deng-1.9.0-beta4/deng-1.9.0-beta4.tgz > > rename it to deng-bin-1.9.0-beta4.tgz, and stick it in /usr/portage/distfiles > Maybe I am missing something here, but I put the ebuild in my portage overlay dircetory, downlaoded, renamed the deng-bin and put it distfiles, but no matter what I try I can't emerge the file.
(In reply to comment #2) > (In reply to comment #1) > > Created an attachment (id=120487) [edit] > > doomsday-bin-1.9.0_beta4.ebuild > > > > you'll have to download the binary package manually. I got mine from > > http://dotpups.de/dotpups/Games/Doomsday/deng-1.9.0-beta4/deng-1.9.0-beta4.tgz > > > > rename it to deng-bin-1.9.0-beta4.tgz, and stick it in /usr/portage/distfiles > > > Maybe I am missing something here, but > I put the ebuild in my portage overlay dircetory, downlaoded, renamed the > deng-bin and put it distfiles, but no matter what I try I can't emerge the > file. > post your emerge output and I'll see if I can figure it out.
> post your emerge output and I'll see if I can figure it out. > #emerge -pv doomsday-bin Calculating dependencies \ emerge: there are no ebuilds to satisfy "doomsday-bin" #emerge -pv usr/local/portage/games-fps/doomsday/doomsday-bin-1.9.0_beta4.ebuild emerging by path implies --oneshot... adding --oneshot to options. *** emerging by path is broken and may not always work!!! These are the packages that would be merged, in order: Calculating dependencies \ !!! /usr/local/portage/games-fps/doomsday/doomsday-bin-1.9.0_beta4.ebuild is not in a valid portage tree hierarchy or does not exist Looking at file locations #locate doomsday-bin /usr/local/portage/games-fps/doomsday/doomsday-bin-1.9.0_beta4.ebuild #locate deng /usr/portage/distfiles/deng-bin-1.9.0-beta4.tgz Portage won't recognize the file at all! So how do I run the ebuild outside of portage?
(In reply to comment #4) > > post your emerge output and I'll see if I can figure it out. Found the problem I needed to create the correct directory doomsday-bin and put the file in there. It finally emerged. Now to set it up and see if it runs....;)
(In reply to comment #5) > (In reply to comment #4) > > > post your emerge output and I'll see if I can figure it out. > Found the problem I needed to create the correct directory doomsday-bin and put > the file in there. > > It finally emerged. Now to set it up and see if it runs....;) > yes, it should have it's own "doomsday-bin" folder in your overlay, because it is an ebuild separate from the "doomsday" ebuild.
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) After a little work I have all my wads up and running. Doom, Doom2, Plutonia, Tnt, Heteric and Hexen. Now to test and see how stable things are. IMHO this is the best port of Doom I tried. I have wanted this on my amd64 for a long time now.
beta4, old and insecure. Marking WONTFIX.
(In reply to comment #8) > beta4, old and insecure. Marking WONTFIX. > better to just version bump it.
that's a different bug.
