Ok folks (notably Stefan and Alin ;)), here are the ebuilds for the AVM firmware files (as discussed via email). I tried to make it gentoo- and maintainer-friendly as possible! # AVM doesn't release versioned archives for their firmware! # So this ebuild has a 'config' section for easy download # current firmware files and package them into $DISTDIR # for easy upload to gentoo mirrors. # Instructions for version bumping: # # 1. check $HOMEPAGE for latest version # 2. copy old ebuild to new one with new version # 3. run "ebuild <ebuild> config" to download firmware # 4. run "ebuild <ebuild> digest" to create the digest # 5. check if the ebuild works properly # # And if you're a maintainer: # # 6. upload the created "${P}.tar.bz2" to gentoo mirrors # 7. release ebuild Reproducible: Always Steps to Reproduce:
Created attachment 51277 [details] avm-firmware-b1-3.11.03.ebuild Firmware for the AVM cards: B1, B1 PCI, B1 PCI V4.0, B1 PCMCIA
Created attachment 51278 [details] avm-firmware-c2-3.11.06.ebuild Firmware for the AVM C2 card
Created attachment 51279 [details] avm-firmware-c4-3.11.06.ebuild Firmware for the AVM C4 card
Created attachment 51280 [details] avm-firmware-t1-3.09.07.ebuild Firmware for the AVM cards: T1, T1-B
Created attachment 51281 [details] avm-firmware-bluefusb-3.18.39.ebuild Firmware for the AVM BlueFritz! USB card (not needed for v2.0)
Created attachment 51282 [details] isdn-firmware-2004.4.5-r2.ebuild updated isdn-firmware-2004.4.5-r1.ebuild which doesn't install the files of the avm-firmware-* ebuilds.
Can we please continue to have one ebuild for all of the firmware files? It would make more sense to select them by use-flag but a special package for every single firmware seems overkill imo. Best is of course to add the firmware to the appropriate driver ebuilds.
no, it is NOT possible, because the firmare-files are updated independently by AVM and have different version numbers. It would be much more complicated to merge them! If we merge them, we have to maintain some kind of "README" with the version numbers listed, etc. Trust me, you really want seperate ebuilds! It's much easier to handle.
to clarify some mis-understandings: The user don't have to run "ebuild <ebuild> config". This is up to the maintainer. The user just says "emerge <firmware>". The pkg_config() is just a helper for the maintainer for easy download and package the latest firmware. The resulting <firmware>.tar.bz2 have to be uploaded then to the gentoo-mirrors. The problem is, that AVM doesn't release versioned tarballs or such, but only versioned directories on their FTP. And this will unfortunately not change. Using 3rd-party solutions, like SuSE-RPMs, are not really good, since we have to depend on their willingness to update and *release* new RPMs on their FTP. We lose the "freshness" of our packages. So my solution is easy to handle and remains full compatibility to gentoo-portage. To answer another question: it's not very intelligent to package all firmware files into a single tarball. AVM maintains different versions for the firmwares. One for every card. How do you want to version the mega-tarball? With the date of the latest firmware in the tarball? And now imagine, that firmware has a bug and is removed from the AVM FTP. How do you version the downgrade? Furthermore: AVM updates the T1 firmware. But you only have a B1. Do you really want to download 1.1MB for nothing? How do you want to maintain a list of the included versions (which is really needed, if you have one big tarball). Etc. pp. There're only disadvantages in using a single, huge tarball. So my suggested solution is slick, gentoo- and maintainer-friendly and very transparent for the user. Think about it! ;-)
hmm... You misuse config function; it is there to properly configure the package after installation (see man ebuild) But your is intention is nice.
I know that my pkg_config() is some kind of abuse. But there isn't a pkg_download_and_package_avm_stuff(). And pkg_config() is not needed otherwise in these ebuilds. So it's a hack, but a cool one. ;-) It's up to you to ask the core/portage maintainers to add a special keyword for such hacks. The other solution would be a seperate download-script. But where do you store this script? On your local harddisk? Into $FILESDIR for reference? What is, when the maintainers are changing? So, once again, it's a hack but a very usable one.
Stefan, one question. Isn't kind of strange to keep isdn-firmware if we'll have separate ebuils for every kind of isdn firmware? In other words, can you provide the rest of ebuilds for what's left in isdn-firmware?
I can. But not now. I'm sleepy. ;) Gimme some time and I do this. btw: Most of the firmware is part of isdn4k-utils. We dropped it there. Ok, don't hurry. We should find a good solution, finally. The problems started with the AVM firmware not being available in a versioned TAR. So all we do here in this bug is to find some kind of "final", gentoo-friendly and slick solution. I think about it all tomorrow.
sbriesen, genstef... what did you decided? will this bug be fixed or not?
@alin: it will be fixed soon. ;) Give us a few days...
I think, we can close this bug for now. I upgraded isdn-firmware to latest SuSE stuff. Now we have current stuff in portage. If there's a need in future to do it with splitted ebuild, I will do it then.
then this isn't the proper resolution
this one is
ok. ;-)
