- 2006-11-25 : big changes : dependancy to imlib removed, all patches are contained in a single tarball in the distfiles, a new use vanilla to have a plain Fvwm CVS without the patches (except the translucent patchs), and one use per irreversible patch : first-item-under-pointer, thin-geometry-proxy et flux-corner_________________Google+ | Twitter

Out of curiosity, have someone applied those agains the latest cvs? That would save me some time hehehe

If not probably next weekend I'll take a look at it and fix a few rejects, this patchset does not work anymore on the last cvs since some weeks ago. Some patches might be useless now. I think the stippled bars one have been merged, I will have to look at the source and changelog.

Too much changes in upstream, none of the patches works. And i'm not able to correct them.
Moreover, i don't use Fvwm anymore since i'm now using E17 so i don't think about maintening this ebuild anymore for the moment, sorry ..._________________Google+ | Twitter

I had some time this evening, and got my hands on the task. Most patches applied with just some fuzz, only the translucency patch, the thin resize one, and the rounded corners patch, gave some trouble. This last was the worse, cause the FvwmWindow struct has changed, and I knew nothing about the fvwm internals. So I had to dig a bit, but finally I found the new names for everything, after that and a couple of rejects I made the thing work.

If you download the overlay you don't need the patchset for anything unless you want to look into the patch. The ebuild should download the patchset automatically for you. You can also download it yourself and put it in distfiles. The links might not work at times cause those are hosted on my home machine, so, if it doesn't work, wait a couple of hours and try again. It is usually always on, though.

Regards.

PS. Those patchs are not mine, I just modified a couple of them to addapt them to the current cvs, and fixed a dozen or so of rejects. So, I have no idea how well/bad they are programmed, and I dont have any idea either if I introduced any bug at all. I just compiled and it all seems to work fine so far. But I don't use all the fancy features, so, something might be broken.

Patches cleaned. I left some stupid crap behind the first time that broke again against the cvs today. All should work now. The urls above are still valid (I will not change the date in the patch filename, I am too lazy to edit the ebuild again and all that stuff). I however, also redigested and repacked the ebuild.

If you have any problem, delete the fvwm-patchset-20070101.tar.gz file in your distfiles, so the ebuild will download the new -updated- one.

As the log is huge, I put it here._________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I know that it broke, today or yesterday was a huge (well, relavitely big) commint on the fvwm cvs repository. I will fix the transparency patch (and probably any other patch that will also break) and offer a new ebuild and patchset soon. Stay tuned. If I can't today, then I will do it tomorrow for sure.

I know that it broke, today or yesterday was a huge (well, relavitely big) commint on the fvwm cvs repository. I will fix the transparency patch (and probably any other patch that will also break) and offer a new ebuild and patchset soon. Stay tuned. If I can't today, then I will do it tomorrow for sure.

Regards.

Thank you for all your work. But don't stress for me, I can wait. I added

Code:

ECVS_UP_OPTS="-D 20070110"
ECVS_CO_OPTS="-D 20070110"

in your ebuild in order to get fvwm to compile with the patchset._________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I know that it broke, today or yesterday was a huge (well, relavitely big) commint on the fvwm cvs repository. I will fix the transparency patch (and probably any other patch that will also break) and offer a new ebuild and patchset soon. Stay tuned. If I can't today, then I will do it tomorrow for sure.

Regards.

Thank you for all your work. But don't stress for me, I can wait. I added

Code:

ECVS_UP_OPTS="-D 20070110"
ECVS_CO_OPTS="-D 20070110"

in your ebuild in order to get fvwm to compile with the patchset.

It seems that the cvs repo is really active today, I will wait a day or two before cleaning the patchset against it. Since if I do it right now it might not work tomorrow. Using a previous snapshot will work or course, good idea

I've updated the translucency patch to the current cvs. This both fixes applying against the resent update order changes and fixes a double popdown which would happen with the patch in the overlay since it was updated to menu bindings. (If a translucent menu moves while another menu is visible above it that menu is popped down. If that isn't handled correctly in other places the menu would popdown again resulting in breakage of style usage counts.)
http://www.dd.chalmers.se/~griph/fvwm-2.5.22-cvs-28-Jan-2007-translucency.diff.gz

I did not have the time to mess up with the thing, and I did well looking here before getting my hands on the patch hehe, the work was already done. Thank you.

It turned out that this was the only patch that broke with the last commits, that's nice, I thought that something more should have broken, but it was not the case. Well, less work to do

So, I just substituted the original translucency patch with yours and it seems to work like a charm. The old links are still valid, I just put your patch there and redigested, the other patchset has not changed at all.

That is pretty weird. I can't guess why it is failing to patch on your system. Are you sure that you are using THIS ebuild and not any other one that is in any other overlay (maybe via layman or something) ?? I just did this, to make sure that I use that ebuild and not a different version on my box, and all seems successful:

I did it just now, and it works as you can see. I don't know why it is failing in your case. Did you modify the ebuild to get a previous release from CVS instead of the latest like Dominique_71 suggested above? That would be another possibility and would make the patch fail for sure. It is the only thing I can think of.

EDIT2, you need the whole tarball, not just the ebuild, because in this case it is the tranlucency patch the culprit, which is into the files subdir into that tarball. Fetching only the ebuild will not work. In fact, the ebuild has not changed at all, it is the patch which changed from the previous release to this one. All the link to the fvwm-cvs-overlay tarball in this thread point to the same file. So, you have no chance to mess with incorrect/outdated tarballs, you just need to unpack it as a whole, as I do in the code above.

I am still learning cvs, and I just see at when using the -D option as I suggested, it will leave permanently in the local copy. So, you have to remove ${PORTDIR}/distfiles/cvs-src/fvwm and the new ebuild must work._________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I am still learning cvs, and I just see at when using the -D option as I suggested, it will leave permanently in the local copy. So, you have to remove ${PORTDIR}/distfiles/cvs-src/fvwm and the new ebuild must work.

Well, then that could be the problem that ygwin was having. Thanks for pointing it out, I use CVS a lot, but -D is one of those few params that I never felt the need to use, so I really did not know what the problem could be, though a "messed" local CVS copy was one of my suspects. It seems that once you use -D, it makes the date sticky on the local copy, so further updates on that same copy will use that date and will not allow you to use code that is marked with a later date.

I use and contribute a little on the Pro-Audio overlay. I am interested to install this ebuild in this overlay too, but I think at I will use a "-D some_date" cvs option in it, that just to be sure at it will work at anytime. And it will be simpler to do so and respect the keyword gentoo policy inside the overlay, because I want to add one (or more if I get the time or if other will contribute) fvwm-crystal recipe customized for use with the overlay, and crystal is already in portage._________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

at the beginning of the ebuild (after inherit or something like that). That because it make no sens at the ebuild first try to download the patches at gentoo mirrors. And the gentoo devs don't like it._________________[[[ To any NSA and FBI agents reading that text: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]