Re: [gentoo-user] Re: XFCE weather plugin does not work
On 10/18/2014 02:37 AM, David W Noon wrote: I have prepared some patches from the Xfce repository with line addressing to match the Gentoo sources tarball. I attach a tarball of theses patches that can be untarred in /etc/portage/patches/ applied. thank you
Re: [gentoo-user] Re: XFCE weather plugin does not work
On Fri, 17 Oct 2014 23:37:16 +0100
David W Noon dwn...@ntlworld.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2014 22:33:45 +0100, Neil Bothwick (n...@digimed.co.uk)
wrote about Re: [gentoo-user] Re: XFCE weather plugin does not work
(in 20141017223345.16c96...@digimed.co.uk):
On Fri, 17 Oct 2014 21:13:52 + (UTC), James wrote:
And last, can any patch that ends in .patch be applied to the
intended ebuild or does the gentoo ebuild auther have to put some
special code into an (EAPI-5) ebuild to facilitate user patches?
AFAIR the ebuild simply has to call epatch_user() in src_unpack()
and any matching patches in /etc/portage/patches are applied.
The usual place is src_prepare().
I have prepared some patches from the Xfce repository with line
addressing to match the Gentoo sources tarball. I attach a tarball of
theses patches that can be untarred in /etc/portage/patches/.
I have unpacked your patches to /etc/portage/patches as described here:
http://wiki.gentoo.org/wiki//etc/portage/patches
and then run # emerge xfce4-weather-plugin
After restarting xfce4, the weather-plugin started to work. Thank you.
Nevertheless, just
# emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
instead of # emerge xfce4-weather-plugin
did not worked.
The ebuild should have the following lines added:
src_prepare() {
epatch_user
}
I have not done this relying on the promise by Greg Kubaryk
that the ebuild is epatch_user enabled.
Don't forget to redo the manifest for the ebuild.
I never dealt with ebuilds on a maintaner level.
So, may I ask if it is really necessary and for which purpose.
Regards,
Dave [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlRBmhwACgkQRQ2Fs59Psv8YHgCghXa931NC2rJSa8394L2FvZGB
UIAAoIiiIpd7PktyaQE9Av/RxRYjnLE0
=68v7
-END PGP SIGNATURE-
Re: [gentoo-user] Re: XFCE weather plugin does not work
On Sat, 18 October 2014, at 8:03 am, Gevisz gev...@gmail.com wrote: I have unpacked your patches to /etc/portage/patches as described here: http://wiki.gentoo.org/wiki//etc/portage/patches and then run # emerge xfce4-weather-plugin After restarting xfce4, the weather-plugin started to work. Thank you. Nevertheless, just # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world instead of # emerge xfce4-weather-plugin did not worked. I think that's because the ebuild's version number didn't change. Hence the package wasn't included when you told portage to run an update - when you told portage explicitly to install the latest xfce4-weather-plugin it found the patches. Stroller.
Re: [gentoo-user] Re: XFCE weather plugin does not work
On Sat, 18 Oct 2014 10:03:10 +0300, Gevisz (gev...@gmail.com) wrote
about Re: [gentoo-user] Re: XFCE weather plugin does not work (in
544210d1.22a0700a.56bc.5...@mx.google.com):
On 18/10/14 08:03, Gevisz wrote:
[snip]
I have unpacked your patches to /etc/portage/patches as described here:
http://wiki.gentoo.org/wiki//etc/portage/patches
and then run # emerge xfce4-weather-plugin
After restarting xfce4, the weather-plugin started to work. Thank you.
You're welcome. The Xfce developers did the hard yakka, I simply
massaged the patches so that they would apply cleanly on Gentoo systems.
Nevertheless, just
# emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
instead of # emerge xfce4-weather-plugin
did not worked.
That's because the plugin's version/release number has not been
modified, so emerge will not process it.
The ebuild should have the following lines added:
src_prepare() {
epatch_user
}
I have not done this relying on the promise by Greg Kubaryk
that the ebuild is epatch_user enabled.
That can be a bit variable. I still put the epatch_user command in
explicitly, just to be certain.
Don't forget to redo the manifest for the ebuild.
I never dealt with ebuilds on a maintaner level.
So, may I ask if it is really necessary and for which purpose.
If you modify the ebuild then you *must* update the manifest. If you
don't modify the ebuild then there is no need.
--
Regards,
Dave [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Re: [gentoo-user] Re: XFCE weather plugin does not work
On Sat, 18 Oct 2014 17:18:34 +0100
David W Noon dwn...@ntlworld.com wrote:
On Sat, 18 Oct 2014 10:03:10 +0300, Gevisz (gev...@gmail.com) wrote
about Re: [gentoo-user] Re: XFCE weather plugin does not work (in
544210d1.22a0700a.56bc.5...@mx.google.com):
On 18/10/14 08:03, Gevisz wrote:
[snip]
I have unpacked your patches to /etc/portage/patches as described here:
http://wiki.gentoo.org/wiki//etc/portage/patches
and then run # emerge xfce4-weather-plugin
After restarting xfce4, the weather-plugin started to work. Thank you.
You're welcome. The Xfce developers did the hard yakka, I simply
massaged the patches so that they would apply cleanly on Gentoo systems.
Thank you anyway. :)
But may I ask you if applying those patches could result
in disappearing an alternative keyboard layout?
I guess not, but somehow I've got that result after updating libidn packet
and applying these patches afterwards. :(
The details are in the An alternative keyboard layout is lost thread.
Nevertheless, just
# emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
instead of # emerge xfce4-weather-plugin
did not worked.
That's because the plugin's version/release number has not been
modified, so emerge will not process it.
Ok, I've got it. :)
The ebuild should have the following lines added:
src_prepare() {
epatch_user
}
I have not done this relying on the promise by Greg Kubaryk
that the ebuild is epatch_user enabled.
That can be a bit variable. I still put the epatch_user command in
explicitly, just to be certain.
Don't forget to redo the manifest for the ebuild.
I never dealt with ebuilds on a maintaner level.
So, may I ask if it is really necessary and for which purpose.
If you modify the ebuild then you *must* update the manifest. If you
don't modify the ebuild then there is no need.
Do you mean that putting the patches into /etc/portage/patches/ directory
and emerging the packet does not change the corresponding ebuild?
According to my experience, it is not the case because, reemerging the
xfce4-weather-plugin with the patches deleted from /etc/portage/patches/
directory, I've still got the working plugin and, only after unmerging it
and re-emerging it again without the patches, I returned to its no-data
condition.
(But, as it did not helped me to return my alternative keyboard layout,
I re-emerged the plugin back, with the patches.)
Re: [gentoo-user] Re: XFCE weather plugin does not work
On Sat, 18 Oct 2014 17:18:34 +0100, David W Noon wrote:
I have not done this relying on the promise by Greg Kubaryk
that the ebuild is epatch_user enabled.
That can be a bit variable. I still put the epatch_user command in
explicitly, just to be certain.
You don't need to modify the ebuild to do that. Put this
in /etc/portage/env/category/package
post_src_unpack() {
cd ${S}
epatch_user
}
You can use unpack or prepare. The difference is that the former runs
immediately before the prepare function in the ebuild, the latter
immediately after. Not only does it save manifesting the ebuild each time
you modify it, it saves having the remember to modify it at all after an
update. More importantly, your work is not destroyed on the next sync.
--
Neil Bothwick
I can't walk on water, but I can stagger on alcohol.
signature.asc
Description: PGP signature
Re: [gentoo-user] Re: XFCE weather plugin does not work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 18 Oct 2014 21:18:36 +0100, Neil Bothwick (n...@digimed.co.uk)
wrote about Re: [gentoo-user] Re: XFCE weather plugin does not work
(in 20141018211836.63981...@digimed.co.uk):
On Sat, 18 Oct 2014 17:18:34 +0100, David W Noon wrote:
I have not done this relying on the promise by Greg Kubaryk
that the ebuild is epatch_user enabled.
That can be a bit variable. I still put the epatch_user command
in explicitly, just to be certain.
You don't need to modify the ebuild to do that. Put this in
/etc/portage/env/category/package
post_src_unpack() { cd ${S} epatch_user }
You can use unpack or prepare. The difference is that the former
runs immediately before the prepare function in the ebuild, the
latter immediately after. Not only does it save manifesting the
ebuild each time you modify it, it saves having the remember to
modify it at all after an update. More importantly, your work is
not destroyed on the next sync.
One can also use /etc/portage/bashrc and enable epatch_user on all
ebuilds. But neither of these is what I want.
I put the src_prepare() function into the specific ebuilds that I want
to install patches, and I avoid having it in ebuilds where I don't
want patches applied. The reason for this is that I create quite a
few patches overall. Many of these are a bit flakey, so I don't want
them applied to what I view as a production system, except under
controlled circumstances. To that end, I maintain my own Portage
tree, exempted from emerge --sync, that has the epatch_user included
in its ebuilds where needed. This, in turn, allows me to keep
experimental patches in /etc/portage/patches without the threat of
them turning up in a normal emerge run.
I accept that this is not a normal user's use case, but I'm not really
a normal user.
- --
Regards,
Dave [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlRC0oMACgkQRQ2Fs59Psv+H1ACfQ4mIJl8ie5JIwVtLwOImjOii
DTQAnR8SmAg/P/hrtcanyDHm+0K+O9z0
=iaRu
-END PGP SIGNATURE-
Re: [gentoo-user] Re: XFCE weather plugin does not work
On Sat, 18 Oct 2014 21:50:11 +0100, David W Noon wrote: You can use unpack or prepare. The difference is that the former runs immediately before the prepare function in the ebuild, the latter immediately after. Not only does it save manifesting the ebuild each time you modify it, it saves having the remember to modify it at all after an update. More importantly, your work is not destroyed on the next sync. One can also use /etc/portage/bashrc and enable epatch_user on all ebuilds. But neither of these is what I want. I think globally enabling it in bashrc is a little too risky for me. I only use that file to register a die hook so I know when an ebuild fails. I put the src_prepare() function into the specific ebuilds that I want to install patches, and I avoid having it in ebuilds where I don't want patches applied. Isn't that the point of /etc/portage/env? You can enable what you want when you want. Either for all versions of a package or only one. I accept that this is not a normal user's use case, but I'm not really a normal user. Normal is optional, do whatever works for you. I sometimes use portage/env and sometimes copy the ebuild to my local overlay for modification. Each case is different. -- Neil Bothwick A good pun is its own reword. signature.asc Description: PGP signature
[gentoo-user] Re: XFCE weather plugin does not work
Stroller stroller at stellar.eclipse.co.uk writes: If so, may I ask supporters to make the corresponding changes to the ebuild. There's already a bug for this on Gentoo's tracker: https://bugs.gentoo.org/show_bug.cgi?id=524850 I think that last comment by Greg Kubaryk about the ebuild being epatch_user enabled means you can just download those two patches (google for 1ff71… and 7df30…) and put them in the right /etc/portage subdirectory to have them applied automatically. Stroller. Well I aware of the movement in EAPI-6 [1] to support user patching. But, I think Stroller is talking about epatch_user doc here ? [2] Another question. How can you tell whether a package (ebuild) supports user patching? What EAPI rev did user patching first appear? And last, can any patch that ends in .patch be applied to the intended ebuild or does the gentoo ebuild auther have to put some special code into an (EAPI-5) ebuild to facilitate user patches? Some docs or general discussion would be keen. Like user patches surviving an upgrade of the (patched) package? Or what if the next package upgrade includes a better version of the patch, but it performs a similar function. Or what if the patch you add becomes a stale (version/fork); how do you know or do you have to remind yourself to follow the development details of that (ebuild) package? curiously, James [1] http://wiki.gentoo.org/wiki/Future_EAPI/EAPI_6_tentative_features [2] http://wiki.gentoo.org/wiki//etc/portage/patches
Re: [gentoo-user] Re: XFCE weather plugin does not work
On Fri, 17 Oct 2014 21:13:52 + (UTC), James wrote: And last, can any patch that ends in .patch be applied to the intended ebuild or does the gentoo ebuild auther have to put some special code into an (EAPI-5) ebuild to facilitate user patches? AFAIR the ebuild simply has to call epatch_user() in src_unpack() and any matching patches in /etc/portage/patches are applied. -- Neil Bothwick Don't let your mind wander, it's too little to be let out alone. signature.asc Description: PGP signature
Re: [gentoo-user] Re: XFCE weather plugin does not work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2014 22:33:45 +0100, Neil Bothwick (n...@digimed.co.uk)
wrote about Re: [gentoo-user] Re: XFCE weather plugin does not work
(in 20141017223345.16c96...@digimed.co.uk):
On Fri, 17 Oct 2014 21:13:52 + (UTC), James wrote:
And last, can any patch that ends in .patch be applied to the
intended ebuild or does the gentoo ebuild auther have to put some
special code into an (EAPI-5) ebuild to facilitate user patches?
AFAIR the ebuild simply has to call epatch_user() in src_unpack()
and any matching patches in /etc/portage/patches are applied.
The usual place is src_prepare().
I have prepared some patches from the Xfce repository with line
addressing to match the Gentoo sources tarball. I attach a tarball of
theses patches that can be untarred in /etc/portage/patches/. The
ebuild should have the following lines added:
src_prepare() {
epatch_user
}
Don't forget to redo the manifest for the ebuild.
- --
Regards,
Dave [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlRBmhwACgkQRQ2Fs59Psv8YHgCghXa931NC2rJSa8394L2FvZGB
UIAAoIiiIpd7PktyaQE9Av/RxRYjnLE0
=68v7
-END PGP SIGNATURE-
weather_patches.tgz
Description: application/compressed-tar
Re: [gentoo-user] Re: XFCE weather plugin does not work
On 17 October 2014 23:37:16 BST, David W Noon dwn...@ntlworld.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2014 22:33:45 +0100, Neil Bothwick (n...@digimed.co.uk)
wrote about Re: [gentoo-user] Re: XFCE weather plugin does not work
(in 20141017223345.16c96...@digimed.co.uk):
On Fri, 17 Oct 2014 21:13:52 + (UTC), James wrote:
And last, can any patch that ends in .patch be applied to the
intended ebuild or does the gentoo ebuild auther have to put some
special code into an (EAPI-5) ebuild to facilitate user patches?
AFAIR the ebuild simply has to call epatch_user() in src_unpack()
and any matching patches in /etc/portage/patches are applied.
The usual place is src_prepare().
I have prepared some patches from the Xfce repository with line
addressing to match the Gentoo sources tarball. I attach a tarball of
theses patches that can be untarred in /etc/portage/patches/. The
ebuild should have the following lines added:
src_prepare() {
epatch_user
}
Don't forget to redo the manifest for the ebuild.
- --
Regards,
Dave [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlRBmhwACgkQRQ2Fs59Psv8YHgCghXa931NC2rJSa8394L2FvZGB
UIAAoIiiIpd7PktyaQE9Av/RxRYjnLE0
=68v7
-END PGP SIGNATURE-
Yes, src_prepare, I was working from memory, although src_unpack usually works
too. You don't need to modify the ebuilds in many cases. You can simply define
src_prepare, or src_unpack, in /etc/portage/env for that ebuild.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
[gentoo-user] Re: XFCE weather plugin does not work
Neil Bothwick neil at digimed.co.uk writes: Thanks! I'll have to give this a whirl. I would be interested to see how things are organized under EAPI-6. thanks again, James
