small version bump, made files no longer publically distributed optional.
Created attachment 9391 [details] tbass/tbass-20030204.ebuild
Created attachment 9392 [details, diff] /tbass/files/tbass-20030204-tech-verilog-configure.patch
Created attachment 9393 [details, diff] tbass/files/tbass-20030204-tech-xilinx-configure.patch
Created attachment 9529 [details] tbass/tbass-20030204.ebuild added espresso-ab dependency to ebuild.
Created attachment 9558 [details] app-sci/tbass/tbass-20030204.ebuild discovered extra runtime dep
Hi Chris. Thanks for your submission! I have processed and committed the ebuild. Please test. I see that the 3.1.1 version of balsa has been released. Is this newer than this snapshot? If yes, are there any more dastic changes, like with this one? However to tell the truth, I am not sure what to do about the naming. 3.1.1 is going to be perceived as older than 20030204. Depending on how often releases are made it may be better to switch to the release numbers. However I remember previous balsa submitter saying that I should rely on snapshot, since releases are not that common. In this case we might be better sticking with snapshots.. Actually looking at the date when this 3.1.1 tarball was last modified (Feb 27) I think that we might not need to worry about this yet. I wouldn't expect too much changes to be made in that timeframe. On the other hand stable releases are always prefered to snapshot. What do you think? George
Created attachment 11069 [details] app-sci/tbass/tbass-20030318.ebuild Sorry about this but there was a serious bug in the balsa-20030204 snapshot. I've attached an ebuild for a slightly newer snapshot, its the same in every respect, only the tech-verilog-${PV} has changed to tech-verilog-20030204 and of course the name of the ebuild to tbass-20030318.ebuild. The patches in files/ will need renaming to 20030318 instead of 20030204. Balsa is being constantly worked on. Releases are pretty rare and tend to be out of date quickly (people update to releases, find bugs, get fixed in cvs..). Its better to stick to snapshots for the moment.
Hi Chris. Sorry for the delay, looks like I did not get notification from bugzilla :(. I processed and committed ebuild, please test. Just one thing: that previous version number it was used in like 10 different places throughout the ebuild. I introduced a var VerilogV, and chaned ebuild to use it instead of plain-text version numbers. Also, I changed the patch-lines to use ${PN}-${VerilogV} to avoid unnecessarily duplicating the patches. George
in stable
Fixed DEPEND to point to >=lard-2.0.15 in three ebuilds, following the masking of prerelease lard version. Reclosing the bug. George
