El jue, 17-01-2013 a las 08:31 -0800, Zac Medico escribió:
On 01/17/2013 08:00 AM, Pacho Ramos wrote:
Another try ;)
Looks good to me.
+ 20 Jan 2013; Pacho Ramos pa...@gentoo.org +readme.gentoo.eclass:
+ Finally commit readme.gentoo.eclass to create a README.gentoo doc
file
+ recording
El lun, 14-01-2013 a las 01:29 -0800, Zac Medico escribió:
On 01/13/2013 04:59 AM, Pacho Ramos wrote:
El dom, 13-01-2013 a las 04:54 -0800, Zac Medico escribió:
On 01/13/2013 04:18 AM, Pacho Ramos wrote:
What about this approach?
You should use ${SLOT%/*}, in order to exclude the
On 01/17/2013 07:17 AM, Pacho Ramos wrote:
El lun, 14-01-2013 a las 01:29 -0800, Zac Medico escribió:
On 01/13/2013 04:59 AM, Pacho Ramos wrote:
El dom, 13-01-2013 a las 04:54 -0800, Zac Medico escribió:
On 01/13/2013 04:18 AM, Pacho Ramos wrote:
What about this approach?
You should use
El jue, 17-01-2013 a las 07:47 -0800, Zac Medico escribió:
[...]
Here are a few problems I see with readme.gentoo_print_elog:
1) contains duplication of code
2) [[ -f ${FILESDIR}/README.gentoo-${SLOT%/*} ]] condition seems
wrong, shouldn't it just use [[ -f ${T}/README.gentoo ]] since
On 01/17/2013 08:00 AM, Pacho Ramos wrote:
Another try ;)
Looks good to me.
--
Thanks,
Zac
On Thu, 17 Jan 2013 07:47:18 -0800
Zac Medico zmed...@gentoo.org wrote:
REPLACING_VERSIONS always refers to packages with identical SLOT to
the current package
No it doesn't. If you have foo-1:a and foo-2:b installed, and then you
install foo-1:b, it replaces both 1:a and 2:b.
--
Ciaran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/01/13 11:00 AM, Pacho Ramos wrote:
Another try ;)
There doesn't seem to be any logic here to check if the README.gentoo
that was previously installed has differed from the one that will be
installed (if they differ then the changes
El jue, 17-01-2013 a las 11:54 -0500, Ian Stakenvicius escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/01/13 11:00 AM, Pacho Ramos wrote:
Another try ;)
There doesn't seem to be any logic here to check if the README.gentoo
that was previously installed has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/01/13 12:02 PM, Pacho Ramos wrote:
How could we handle different compressors people can use?
Depending on that README.gentoo will change its name ending with
gz, bz2, xz... Maybe we could use README.gentoo*...
Right; I didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/01/13 11:47 AM, Ciaran McCreesh wrote:
On Thu, 17 Jan 2013 07:47:18 -0800 Zac Medico zmed...@gentoo.org
wrote:
REPLACING_VERSIONS always refers to packages with identical SLOT
to the current package
No it doesn't. If you have foo-1:a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 17 Jan 2013 12:14:38 -0500
Ian Stakenvicius a...@gentoo.org wrote:
On 17/01/13 11:47 AM, Ciaran McCreesh wrote:
On Thu, 17 Jan 2013 07:47:18 -0800 Zac Medico zmed...@gentoo.org
wrote:
REPLACING_VERSIONS always refers to packages with
On 01/17/2013 08:47 AM, Ciaran McCreesh wrote:
On Thu, 17 Jan 2013 07:47:18 -0800
Zac Medico zmed...@gentoo.org wrote:
REPLACING_VERSIONS always refers to packages with identical SLOT to
the current package
No it doesn't. If you have foo-1:a and foo-2:b installed, and then you
install
El jue, 17-01-2013 a las 12:11 -0500, Ian Stakenvicius escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/01/13 12:02 PM, Pacho Ramos wrote:
How could we handle different compressors people can use?
Depending on that README.gentoo will change its name ending with
gz,
On 01/13/2013 04:59 AM, Pacho Ramos wrote:
El dom, 13-01-2013 a las 04:54 -0800, Zac Medico escribió:
On 01/13/2013 04:18 AM, Pacho Ramos wrote:
What about this approach?
You should use ${SLOT%/*}, in order to exclude the sub-slot, because you
don't care about the sub-slot and the slash
El sáb, 12-01-2013 a las 04:49 -0800, Zac Medico escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/12/2013 02:34 AM, Pacho Ramos wrote:
El sáb, 12-01-2013 a las 02:01 -0800, Zac Medico escribió:
On 01/12/2013 01:46 AM, Pacho Ramos wrote:
El mié, 09-01-2013 a las 12:04 -0800,
On 01/13/2013 04:18 AM, Pacho Ramos wrote:
What about this approach?
You should use ${SLOT%/*}, in order to exclude the sub-slot, because you
don't care about the sub-slot and the slash would cause problems.
--
Thanks,
Zac
El dom, 13-01-2013 a las 04:54 -0800, Zac Medico escribió:
On 01/13/2013 04:18 AM, Pacho Ramos wrote:
What about this approach?
You should use ${SLOT%/*}, in order to exclude the sub-slot, because you
don't care about the sub-slot and the slash would cause problems.
Thanks, updated eclass
El mié, 09-01-2013 a las 12:04 -0800, Zac Medico escribió:
On 01/09/2013 11:53 AM, Pacho Ramos wrote:
This changes the name of eclass to readme.gentoo.eclass and gets
information from ${FILESDIR}/README.gentoo
What if there are multiple versions/slots that have different
README.gentoo
On 01/12/2013 01:46 AM, Pacho Ramos wrote:
El mié, 09-01-2013 a las 12:04 -0800, Zac Medico escribió:
On 01/09/2013 11:53 AM, Pacho Ramos wrote:
This changes the name of eclass to readme.gentoo.eclass and gets
information from ${FILESDIR}/README.gentoo
What if there are multiple
El sáb, 12-01-2013 a las 02:01 -0800, Zac Medico escribió:
On 01/12/2013 01:46 AM, Pacho Ramos wrote:
El mié, 09-01-2013 a las 12:04 -0800, Zac Medico escribió:
On 01/09/2013 11:53 AM, Pacho Ramos wrote:
This changes the name of eclass to readme.gentoo.eclass and gets
information from
El sáb, 12-01-2013 a las 11:34 +0100, Pacho Ramos escribió:
[...]
Thank for explaining me how to do that. The problem is that I doubt if
it would really be useful as we usually won't need whan README.gentoo
per version, only to update if for some special cases from time to
time :/
[...]
whan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/12/2013 02:34 AM, Pacho Ramos wrote:
El sáb, 12-01-2013 a las 02:01 -0800, Zac Medico escribió:
On 01/12/2013 01:46 AM, Pacho Ramos wrote:
El mié, 09-01-2013 a las 12:04 -0800, Zac Medico escribió:
On 01/09/2013 11:53 AM, Pacho Ramos wrote:
On 2013-01-12, at 7:49 AM, Zac Medico zmed...@gentoo.org wrote:
Still, it maybe it would be reasonable to use a different
README.gentoo for each SLOT, it there's more than one?
especially since that means no special logic is necessary when cleaning them up
on uninstall...
El lun, 07-01-2013 a las 10:34 +0100, Pacho Ramos escribió:
[...]
This will install a README.gentoo file
But there are still pending issues I don't know how to handle:
- Eclass was originally oriented to cover those kind of messages that
could be shown by elog first time the package is
On 01/09/2013 11:53 AM, Pacho Ramos wrote:
This changes the name of eclass to readme.gentoo.eclass and gets
information from ${FILESDIR}/README.gentoo
What if there are multiple versions/slots that have different
README.gentoo content? Maybe the eclass should accommodate that somehow?
--
El mié, 09-01-2013 a las 12:04 -0800, Zac Medico escribió:
On 01/09/2013 11:53 AM, Pacho Ramos wrote:
This changes the name of eclass to readme.gentoo.eclass and gets
information from ${FILESDIR}/README.gentoo
What if there are multiple versions/slots that have different
README.gentoo
El mié, 09-01-2013 a las 22:15 +0100, Pacho Ramos escribió:
El mié, 09-01-2013 a las 12:04 -0800, Zac Medico escribió:
On 01/09/2013 11:53 AM, Pacho Ramos wrote:
This changes the name of eclass to readme.gentoo.eclass and gets
information from ${FILESDIR}/README.gentoo
What if there
Hi,
Quoting Pacho Ramos (2013-01-07 10:34:52)
- Eclass was originally oriented to cover those kind of messages that
could be shown by elog first time the package is merged and, later,
rely on people reading that README.gentoo
This would be good - show README.gentoo for first time, and treat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2013 11:46 AM, Amadeusz Żołnowski wrote:
Hi,
Quoting Pacho Ramos (2013-01-07 10:34:52)
- Eclass was originally oriented to cover those kind of messages
that could be shown by elog first time the package is merged and,
later, rely on
On Sun, Jan 6, 2013 at 8:54 PM, Zac Medico zmed...@gentoo.org wrote:
On 01/06/2013 05:36 PM, Michael Mol wrote:
On Jan 6, 2013 8:32 PM, Zac Medico zmed...@gentoo.org
mailto:zmed...@gentoo.org wrote:
On 01/06/2013 01:04 AM, Ralph Sennhauser wrote:
On Fri, 4 Jan 2013 23:34:59 -0600
Donnie
On 01/07/2013 05:35 PM, Michael Mol wrote:
On Sun, Jan 6, 2013 at 8:54 PM, Zac Medico zmed...@gentoo.org wrote:
On 01/06/2013 05:36 PM, Michael Mol wrote:
On Jan 6, 2013 8:32 PM, Zac Medico zmed...@gentoo.org
mailto:zmed...@gentoo.org wrote:
On 01/06/2013 01:04 AM, Ralph Sennhauser wrote:
On 01/06/2013 01:04 AM, Ralph Sennhauser wrote:
On Fri, 4 Jan 2013 23:34:59 -0600
Donnie Berkholz dberkh...@gentoo.org wrote:
On 10:26 Sat 22 Dec , Pacho Ramos wrote:
Hello
After seeing:
https://bugs.gentoo.org/show_bug.cgi?id=440214
Looking to a lot of its blockers shows that we
On Jan 6, 2013 8:32 PM, Zac Medico zmed...@gentoo.org wrote:
On 01/06/2013 01:04 AM, Ralph Sennhauser wrote:
On Fri, 4 Jan 2013 23:34:59 -0600
Donnie Berkholz dberkh...@gentoo.org wrote:
On 10:26 Sat 22 Dec , Pacho Ramos wrote:
Hello
After seeing:
On 01/06/2013 05:36 PM, Michael Mol wrote:
On Jan 6, 2013 8:32 PM, Zac Medico zmed...@gentoo.org
mailto:zmed...@gentoo.org wrote:
On 01/06/2013 01:04 AM, Ralph Sennhauser wrote:
On Fri, 4 Jan 2013 23:34:59 -0600
Donnie Berkholz dberkh...@gentoo.org mailto:dberkh...@gentoo.org
wrote:
On Fri, Jan 04, 2013 at 11:34:59PM -0600, Donnie Berkholz wrote:
On 10:26 Sat 22 Dec , Pacho Ramos wrote:
Hello
After seeing:
https://bugs.gentoo.org/show_bug.cgi?id=440214
Looking to a lot of its blockers shows that we are using elog messages
for informing people about
On 10:26 Sat 22 Dec , Pacho Ramos wrote:
Hello
After seeing:
https://bugs.gentoo.org/show_bug.cgi?id=440214
Looking to a lot of its blockers shows that we are using elog messages
for informing people about configuration (like pointing people to
external links to get proper way of
El mar, 01-01-2013 a las 16:01 -0800, Zac Medico escribió:
On 01/01/2013 05:39 AM, Pacho Ramos wrote:
El mar, 01-01-2013 a las 14:32 +0100, Pacho Ramos escribió:
pkg_postinst() {
@@ -48,6 +56,8 @@
elog
fi
+ echo ${CONFIGURATION_INSTRUCTIONS} | fmt | while read -s
On 01/02/2013 03:48 AM, Pacho Ramos wrote:
El mar, 01-01-2013 a las 16:01 -0800, Zac Medico escribió:
On 01/01/2013 05:39 AM, Pacho Ramos wrote:
El mar, 01-01-2013 a las 14:32 +0100, Pacho Ramos escribió:
pkg_postinst() {
@@ -48,6 +56,8 @@
elog
fi
+ echo
El lun, 31-12-2012 a las 14:53 -0800, Zac Medico escribió:
On 12/31/2012 05:21 AM, Pacho Ramos wrote:
pkg_postinst() {
Some improvements I am not sure how to implement just now:
- What would be the proper way to elog contents
of /usr/share/doc/${PF}/CONFIGURATION.bz2 and, then, allow
El mar, 01-01-2013 a las 14:32 +0100, Pacho Ramos escribió:
[...]
--- /home/pacho/gentoo-x86/sys-power/acpid/acpid-2.0.17.ebuild
2012-11-26 09:20:15.0 +0100
+++ ./acpid-2.0.17.ebuild 2013-01-01 14:30:18.0 +0100
@@ -17,6 +17,11 @@
RDEPEND=selinux? ( sec-policy/selinux-apm
On 01/01/2013 05:39 AM, Pacho Ramos wrote:
El mar, 01-01-2013 a las 14:32 +0100, Pacho Ramos escribió:
pkg_postinst() {
@@ -48,6 +56,8 @@
elog
fi
+echo ${CONFIGURATION_INSTRUCTIONS} | fmt | while read -s ELINE; do
elog ${ELINE}; done
+
#
El dom, 30-12-2012 a las 00:09 +0100, Pacho Ramos escribió:
[...]
I want to have a permanent reference of current elog messages simply
showing configuration tips to:
1. Show them via elog messages only first time package is installed
2. Not need to read ebuild directly once people remove
On 12/31/2012 05:21 AM, Pacho Ramos wrote:
pkg_postinst() {
Some improvements I am not sure how to implement just now:
- What would be the proper way to elog contents
of /usr/share/doc/${PF}/CONFIGURATION.bz2 and, then, allow the following
to be shorter:
if ! has_version
El lun, 24-12-2012 a las 00:30 +0100, Pacho Ramos escribió:
El lun, 24-12-2012 a las 00:17 +0100, Diego Elio Pettenò escribió:
On 23/12/2012 23:54, Pacho Ramos wrote:
The idea would be to make it to be only shown at first message and,
later, rely on people reading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/12/12 00:09, Pacho Ramos wrote:
More examples I saw today when updating: - nvidia-drivers - things
like telling people to add them to video group could be treated in
the same way, the same probably for eselect instructions.
Every game
On 23 December 2012 09:57, Pacho Ramos pa...@gentoo.org wrote:
El sáb, 22-12-2012 a las 13:53 -0800, Zac Medico escribió:
On 12/22/2012 01:46 PM, Markos Chandras wrote:
On 22 December 2012 09:26, Pacho Ramos pa...@gentoo.org wrote:
Hello
After seeing:
On Sun, 2012-12-23 at 12:20 +, Markos Chandras wrote:
But like I said, elog messages are already saved in
/var/log/portage/elog/$cat/$pf so people can
read these. Isn't this the same with what you suggest?
Is that by default? And when was that default added?
I certainly do not have
On 23 December 2012 13:58, Alexandre Rostovtsev tetrom...@gentoo.org wrote:
On Sun, 2012-12-23 at 12:20 +, Markos Chandras wrote:
But like I said, elog messages are already saved in
/var/log/portage/elog/$cat/$pf so people can
read these. Isn't this the same with what you suggest?
Is
On Sun, 2012-12-23 at 08:58 -0500, Alexandre Rostovtsev wrote:
On Sun, 2012-12-23 at 12:20 +, Markos Chandras wrote:
But like I said, elog messages are already saved in
/var/log/portage/elog/$cat/$pf so people can
read these. Isn't this the same with what you suggest?
Is that by
On 12/23/2012 08:35 AM, Brian Dolbec wrote:
On Sun, 2012-12-23 at 08:58 -0500, Alexandre Rostovtsev wrote:
On Sun, 2012-12-23 at 12:20 +, Markos Chandras wrote:
But like I said, elog messages are already saved in
/var/log/portage/elog/$cat/$pf so people can
read these. Isn't this the same
El dom, 23-12-2012 a las 13:36 -0800, Zac Medico escribió:
On 12/23/2012 08:35 AM, Brian Dolbec wrote:
On Sun, 2012-12-23 at 08:58 -0500, Alexandre Rostovtsev wrote:
On Sun, 2012-12-23 at 12:20 +, Markos Chandras wrote:
But like I said, elog messages are already saved in
On 23/12/2012 23:54, Pacho Ramos wrote:
The idea would be to make it to be only shown at first message and,
later, rely on people reading /usr/share/doc/e4rat-xxx/CONFIGURATION
file if they want to remember that tip
So you want in the main documentation a request to read the package
El lun, 24-12-2012 a las 00:17 +0100, Diego Elio Pettenò escribió:
On 23/12/2012 23:54, Pacho Ramos wrote:
The idea would be to make it to be only shown at first message and,
later, rely on people reading /usr/share/doc/e4rat-xxx/CONFIGURATION
file if they want to remember that tip
So
53 matches
Mail list logo
