| Summary: | new ebuild - BEAST - the Bedevilled Sound Engine | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Rigo <rigo> |
| Component: | New packages | Assignee: | Gentoo Sound Team <sound> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | agenkin |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://beast.gtk.org/ | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuild-file
ebuild-file (datafiles beast) New ebuild-file New ebuild-file (Datafiles) new ebuild beast-0.4.1.ebuild |
||
|
Description
Rigo
2002-07-15 07:17:59 UTC
Created attachment 2257 [details]
ebuild-file
Created attachment 2258 [details]
ebuild-file (datafiles beast)
Hi, Rigo: You have not packaged the docs (files AUTHORS, COPYING and the like). Could you please include an explicit src_install() that would package everything useful from the tarball? Thanks. Ofcourse! Any hints/tips/examples please ? (Am learning by doing, so if you could review my enthousiastic work afterwards ;-) ? Created attachment 2311 [details]
New ebuild-file
Do you mean something like this (see new attachment) ? Questione: do I call the 'doman' command every time explicitly, or do most packages make their manual pages automaticly ? Created attachment 2312 [details]
New ebuild-file (Datafiles)
'doman' is only for troff-formatted man pages. The .txt and .faq should probably be installed using 'dodoc'. You need to include "make install" into the src_install(), as in the skel.ebuild. I tried compiling the thing, but get the following during the configure stage: checking for ALSA modules... no - beast driver too old configure: error: unable to find any sound drivers/devices So, what does this thing need to work? Created attachment 2358 [details]
new ebuild
Duh, forgot that one ;-) That's why I said alsa-trouble in the 1st. place... Okay, but who will this ebuild be useful to? Does it require older ALSA or what? How is it possible to test it? Closing this for the lack of feedback. Created attachment 3620 [details]
beast-0.4.1.ebuild
Sorry for the delay...New release, tested with programmer for 3.2...Should be
fine now...
# emerge search beast
Searching...
[ Results for search key : beast ]
[ Applications found : 2 ]
* media-sound/beast
Latest version Available: 0.4.1
Latest version Installed: 0.4.1
Homepage: http://beast.gtk.org
Description: BEAST - the Bedevilled Sound Engine
* media-sound/beast-data
Latest version Available: 0.3
Latest version Installed: 0.3
Homepage: http://beast.gtk.org
Description: BEAST - the Bedevilled Sound Engine (datafiles)
Okay, but now I have to wait until the portage freeze is lifted (after the release of Gentoo 1.4) :(. Thanks. Hi, Rigo: I committed the ebuilds to the portage tree. There were some problems with dependencies, and the ebuild for beast-data was missing "make install". 1. The ebuild installs some documentation under /usr/share/beast/v0.4.1/docs. Those should really go into the standard documentation location (/usr/share/doc/beast-0.4.1/). 2. I noticed that during the compilation the flag "-06" is used. You should honor the user's setting for compilation defaults. It would be nice if you could hack around this. 3. The beast-data ebuild installs some files under /usr/share/beast/v0.3. Is that correct? 4. Also, why are there three directories under /usr/share/beast: v0.3, v0.4 and v0.4.1? The ebuilds are masked for now. It would be nice if you could fix the above problems. Thanks for your submission. 1. The ebuild installs some documentation under /usr/share/beast/v0.4.1/docs. Those should really go into the standard documentation location (/usr/share/doc/beast-0.4.1/). files/docs-reorg-0.5.4.patch is now in portage with the beast-0.5.4.ebuild which addresses this issue. 2. I noticed that during the compilation the flag "-06" is used. You should honor the user's setting for compilation defaults. It would be nice if you could hack around this. More special thought was put into the CFLAGS and CXXFLAGS of this ebuild over time. There are places where environment variables are taken into effect and other parts where specific optimization is included (not just the sweeping -O?s either). Prior -O6 wackiness has been toned to -O3 and again to -O2. 3. The beast-data ebuild installs some files under /usr/share/beast/v0.3. Is that correct? beast-data is no longer relevant at this point in beast's development. 4. Also, why are there three directories under /usr/share/beast: v0.3, v0.4 and v0.4.1? This is also working fine in 0.5.4 with the docs-reorg-0.5.4.patch Pleast test this new ebuild and let me now how things work for you. please test db issue |
