i have two modified ebuilds. the first is wolk-sources-4.1s.ebuild just an update for the wolk-sources server edition. it seems ok and it works on my system. the second is wolk-sources-4.1w.ebuild it is well ugly. 13 extra patches will be applied and so i have 13 more lines of code. i do not like it but it is a good beginning becourse you can see what patches will be applied and comment them out when you won't want them. this patches are offered by one wolk-developer because there won't be a workstation kernel of wolk in the near future. i bzip2ed the 13 patches and tared and bzip2ed the directory. this file sould go to ${DISTDIR} after downloading -> yet it is not implemented in the ebuild. so with this ebuild i need a little help but it is working. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 12550 [details] wolk-sources-4.1s.ebuild
Created attachment 12551 [details] wolk-sources-4.1w.ebuild
Created attachment 12552 [details] wolk-extrapatches-4.1.tar.bz2
sry for being this late: i will offer you now the wolk-sources-4.2s/w.ebuild
Created attachment 12879 [details] wolk-sources-4.2s.ebuild
Created attachment 12880 [details] wolk-sources-4.2w.ebuild
Created attachment 12881 [details] wolk-extrapatches-4.2.tar.bz2
Created attachment 12898 [details] sys-kernel/wolk-server-sources/wolk-server-sources-4.2.ebuild this is the ebuild i did for my self for the server edition of wolk. it allows me to add just another patch, by simply adding text to an variable and have that way the wolk kernel upgraded to a new version. i find it much easyer to maintain then your version. let me know what you think. cheers SteveB
can the title/summary of this bug be changed to include the text 4.2?
steveb: i like you ebuild pretty much. i will change this for wolk-sources-4.2w soon. thank you. too the title is changed
Created attachment 12910 [details] wolk-sources-4.2w.ebuild
i am truly sorry, but the last ebuilds seems not to be as clean as i expected them to. So i updated them and hopefully deleted all bugs. I also made some important changes within the 4.xw line: like steveb's idea of one variable which includes all filenames downloaded from the net and applied to the kernel i am going the same way: i divided the whole wolk-extrapatches in its parts: win4lin, bootsplash, supermount and mipv6. So you can decide which patch you want and which not and this way you don't have to download the whole file(s). With manipulating the EP="..." line in the beginning of the ebuild you can easily decide which patch will be applied by removing the patch name from this line ;) too like the first ones this extra patches have to be placed in the ${DISTFILES} directory. Because this ebuilds are no offical ebuilds, they are cannot be found on the mirrors. So here they come. PS: Thank you steveb
Created attachment 12999 [details] updated: wolk-sources-4.1s.ebuild
Created attachment 13000 [details] updated: wolk-sources-4.1w.ebuild
Created attachment 13001 [details] updated: wolk-sources-4.2w.ebuild
Created attachment 13002 [details, diff] bootsplash-wolk4.1w
Created attachment 13003 [details, diff] bootsplash-wolk4.2w
Created attachment 13004 [details, diff] mipv6-wolk4.1w
Created attachment 13005 [details, diff] mipv6-wolk4.2w
Created attachment 13006 [details, diff] supermount-wolk4.1w
Created attachment 13007 [details, diff] supermount-wolk4.2w
Created attachment 13008 [details, diff] win4lin-wolk4.1w
Created attachment 13009 [details, diff] win4lin-wolk4.2w
Hi In the wolk-4.2w ebuild the ${EP} used in src_unpack() is not set to anyhing? and therefor it does not unpack. tar returns ".tar.bz not found" or some such. Or it missed retrieving something? bus_drivr
David Cozatt: In the beginning of the ebuild line 15 you will find this line: EP="win4lin-wolk4.2w bootsplash-wolk4.2w supermount-wolk4.2w mipv6-wolk4.2w" you must have ALL patchfiles which are included in this line in the ${DISTFILE} directory OR you delete manually one ore more patchname(s) from this line and then it doesn't matter if you have these special patch(es) in the ${DISTFILE} directory. they won't be applied wether they are there or not. Also the patches aren't downloadet yet because they are not on the gentoo download mirrors. these ebuilds aren't official yet.
<snip> >In the beginning of the ebuild line 15 you will find this line: >EP="win4lin-wolk4.2w bootsplash-wolk4.2w supermount-wolk4.2w >mipv6-wolk4.2w" errmm. sowy? :) I had fetched the first without seeing the updated ones. nm. thx. bus_drivr
yes. i'd like to see the new wolk get in. wolk 4.3 was released today.
i am truly sorry, but i am in holidays now ;) but you can easily patch the wolk--server-sources-4.2.ebuild by yourself. Changes: KV=${OKV}-wolk4.2s to KV=${OKV}-wolk4.3s and PATCHEFILES="-wolk4.0s -wolk4.0s-to-4.1s -wolk4.1s-to-4.2s" to PATCHEFILES="-wolk4.0s -wolk4.0s-to-4.1s -wolk4.1s-to-4.2s
i am truly sorry, but i am in holidays now ;) but you can easily patch the wolk--server-sources-4.2.ebuild by yourself. Changes: KV=${OKV}-wolk4.2s to KV=${OKV}-wolk4.3s and PATCHEFILES="-wolk4.0s -wolk4.0s-to-4.1s -wolk4.1s-to-4.2s" to PATCHEFILES="-wolk4.0s -wolk4.0s-to-4.1s -wolk4.1s-to-4.2s wolk4.2s-to-4.3s"
ohh and i come back in the end of july, so maybe steveb or somebody else can change the ebuild and commit it because i have no chance to :( ;)
*** Bug 22779 has been marked as a duplicate of this bug. ***
wolk 4.3 is in.
