On Sun, 2008-10-05 at 23:38 -0700, Josh Saddler wrote:
> Ulrich Mueller wrote:
> >> On Sun, 5 Oct 2008, Robin H Johnson wrote:
> >
> HOMEPAGE="http://this-package-has-no-homepage.gentoo.org/";
> >>> That would impose needless lookups on subdomains of gentoo.org for
> >>> clients trying to
Ulrich Mueller wrote:
>> On Sun, 5 Oct 2008, Robin H Johnson wrote:
>
HOMEPAGE="http://this-package-has-no-homepage.gentoo.org/";
>>> That would impose needless lookups on subdomains of gentoo.org for
>>> clients trying to load the homepage.
>> http://gentoo.org/package-has-no-homepage/ t
> On Sun, 5 Oct 2008, Robin H Johnson wrote:
>> > HOMEPAGE="http://this-package-has-no-homepage.gentoo.org/";
>> That would impose needless lookups on subdomains of gentoo.org for
>> clients trying to load the homepage.
> http://gentoo.org/package-has-no-homepage/ then.
Couldn't a page be cre
> On Mon, 06 Oct 2008, Jorge Manuel B S Vicetto wrote:
> No objections here, just a question. Do you know if the issue with the
> lp:// sources has been fixed in bzr?
Looks like this is working fine with bzr-1.5, so I'll change the
dependency.
Ulrich
"Alec Warner" <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted
below, on Sun, 05 Oct 2008 19:52:48 -0700:
> On Sun, Oct 5, 2008 at 2:55 PM, Thilo Bangert <[EMAIL PROTECTED]>
> wrote:
>>
>> HOMEPAGE="http://this-package-has-no-homepage.gentoo.org/";
>>
> That would impose needless lookups o
On Sun, Oct 05, 2008 at 07:52:48PM -0700, Alec Warner wrote:
> On Sun, Oct 5, 2008 at 2:55 PM, Thilo Bangert <[EMAIL PROTECTED]> wrote:
> > Ciaran McCreesh <[EMAIL PROTECTED]> said:
> >> On Sun, 5 Oct 2008 03:44:20 -0700
> >>
> >> "Robin H. Johnson" <[EMAIL PROTECTED]> wrote:
> >> > Either we need
On Sun, Oct 5, 2008 at 2:55 PM, Thilo Bangert <[EMAIL PROTECTED]> wrote:
> Ciaran McCreesh <[EMAIL PROTECTED]> said:
>> On Sun, 5 Oct 2008 03:44:20 -0700
>>
>> "Robin H. Johnson" <[EMAIL PROTECTED]> wrote:
>> > Either we need special cases to declare that it no longer has a
>> > homepage, or we nee
On Sun, 05 Oct 2008 20:44:51 -0500
Jeremy Olexa <[EMAIL PROTECTED]> wrote:
> I would suggest moving all the "slacking" arches to "experimental"
> until there is desire from the dev community (read: manpower) to
> support a stable tree again. Until then, it seems pretty pointless to
> keep assignin
Friedrich Oslage wrote:
Am Sonntag, den 05.10.2008, 16:26 -0500 schrieb Steev Klimaszewski:
Thoughts? Helps?
Afaik we have 3 types of arches:
- experimental
They are not CCed on stablization bugs and don't do stablizations at
all.
~mips, ~sparc-fbsd and ~x86-fbsd
- unsupported
They are CCe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ulrich.
Ulrich Mueller wrote:
>> On Fri, 21 Mar 2008, Christian Faulhammer wrote:
>
>> "Jorge Manuel B. S. Vicetto" <[EMAIL PROTECTED]>:
>>> With the help of Ingmar we did some cleanup and added support for
>>> eclass-manpages at
>>> http://
Mart Raudsepp kirjoitti:
> On P, 2008-10-05 at 20:34 +0200, Thomas Sachau wrote:
>> Rémi Cardona schrieb:
>>> Thomas Sachau a écrit :
Why not do both (rebuild and install) with the doc useflag and none of
both, if it is not set? Imho
the doc flag is for control of installation for (a
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2008-10-05 23h59 UTC.
Removals:
media-fonts/liberation-fonts-ttf2008-09-30 02:01:51 je_fro
app-emulation/vmware-workstation-tools 2008-09-30 20:13:11 ikelos
dev-tex/extsizes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
This is a revised version of the profile EAPI lables proposal which
has been discussed previously [1].
Please consider a new 'eapi' profile configuration file that will
designate the EAPI to which any package atoms within the files of a
On P, 2008-10-05 at 20:34 +0200, Thomas Sachau wrote:
> Rémi Cardona schrieb:
> > Thomas Sachau a écrit :
> >> Why not do both (rebuild and install) with the doc useflag and none of
> >> both, if it is not set? Imho
> >> the doc flag is for control of installation for (additional) docs, the
> >> wa
Am Sonntag, den 05.10.2008, 16:26 -0500 schrieb Steev Klimaszewski:
>
> Thoughts? Helps?
>
Afaik we have 3 types of arches:
- experimental
They are not CCed on stablization bugs and don't do stablizations at
all.
~mips, ~sparc-fbsd and ~x86-fbsd
- unsupported
They are CCed on stablizations bug
Ciaran McCreesh <[EMAIL PROTECTED]> said:
> On Sun, 5 Oct 2008 03:44:20 -0700
>
> "Robin H. Johnson" <[EMAIL PROTECTED]> wrote:
> > Either we need special cases to declare that it no longer has a
> > homepage, or we need to allow the empty HOMEPAGE.
>
> HOMEPAGE="( )"
HOMEPAGE="http://this-package
Not wanting to start a huge war about what arches are slacking and
which aren't - I asked in -dev on IRC and was told to check out
profiles.desc - based on this information, I closed Bug 208917 which
was about stablizing dbus-glib-0.74. The bug was opened on 04 Feb
2008, and as of today 05 Oct 200
Here is a patch that adds support for shared repositories. Since bzr
is still a bit slow this is quite useful when using multiple branches.
For example I have modified the live emacs(-cvs) ebuild to use the bzr
mirror of emacs instead of cvs. I also have my own emacs branches, and
sometimes want t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 05 Oct 2008 10:11:08 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>> They can call 'die' in global scope. Perhaps it's not the nicest
>> thing to do, but it can be done.
>
> Last time I tried it, Portage behaved rathe
On Sun, 5 Oct 2008 03:44:20 -0700
"Robin H. Johnson" <[EMAIL PROTECTED]> wrote:
> Either we need special cases to declare that it no longer has a
> homepage, or we need to allow the empty HOMEPAGE.
HOMEPAGE="( )"
--
Ciaran McCreesh
signature.asc
Description: PGP signature
081005 Ryan Hill wrote:
> 5 Oct 2008 "Robin H. Johnson" <[EMAIL PROTECTED]> wrote:
>> For projects where the upstream has vanished off the face of the planet
>> but ... the code works fine still, there's problems
>> with either the requirements of HOMEPAGE or the repoman check.
>> Either we need sp
On Sun, 05 Oct 2008 10:11:08 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> They can call 'die' in global scope. Perhaps it's not the nicest
> thing to do, but it can be done.
Last time I tried it, Portage behaved rather horribly with global scope
dies. Is this still the case?
> Considering that t
On Sun, 5 Oct 2008 21:48:09 +0200
Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> All our documentation (devmanual, ebuild howto, skel.ebuild, pms)
> recommends "econf || die".
I've fixed PMS.
--
Ciaran McCreesh
signature.asc
Description: PGP signature
Le dimanche 05 octobre 2008 à 20:34 +0200, Thomas Sachau a écrit :
> Did i say something about disk space? I say, you are using the doc use flag
> in a way that is not
> expected. The global use flag says, it installs additional documentation. But
> your doc use flag does
> not install anything a
> On Sun, 05 Oct 2008, Thomas Sachau wrote:
>> econf \
>> [...]
>> ${myconf} || die
> "|| die" could be dropped
All our documentation (devmanual, ebuild howto, skel.ebuild, pms)
recommends "econf || die".
So maybe you should first make an effort to have it changed there?
I wouldn't consider
Thomas Sachau wrote:
> I just had a user in bugzilla who thought, the developer profile would be for
> software developers,
> not just for gentoo developers. Probably he is not the only one.
>
> What about either adding some big warning on portage output or renaming this
> profile to e.g.
> "gen
Ali Polatel (hawking) schrieb:
> use threads \
> && myconf="${myconf} --with-threads" \
> || myconf="${myconf} --without-threads"
What about an econf option $(use_with threads)?
> econf \
> --with-fpectl \
> --enable-shared \
>
Rémi Cardona schrieb:
> Thomas Sachau a écrit :
>> Why not do both (rebuild and install) with the doc useflag and none of
>> both, if it is not set? Imho
>> the doc flag is for control of installation for (additional) docs, the
>> way it is used for gtk-doc is
>> surely confusing.
>>
>
> Building
Robert Buchholz schrieb:
> On Sunday, 5. October 2008, Ulrich Mueller wrote:
>>> On Sun, 5 Oct 2008, Robert Buchholz wrote:
> It's not. If you want to have default DOCS then you should loop
> through the items and check with [[ -e ]] before trying to
> install them.
So, maybe j
On Sat, 04 Oct 2008 10:17:05 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ryan Hill wrote:
> > Though I'm still not sure what happens when a package is in two
> > unrelated sets..
> >
> > @gnome:
> >RDEPEND=">=gnome-extra/gnome-screensaver
On Sun, 5 Oct 2008 03:44:20 -0700
"Robin H. Johnson" <[EMAIL PROTECTED]> wrote:
> For projects where the upstream has vanished off the face of the
> planet, and the project was reasonably obscure, but the code works
> fine still, there's problems with either the requirements of HOMEPAGE
> or the r
> On Fri, 21 Mar 2008, Christian Faulhammer wrote:
> "Jorge Manuel B. S. Vicetto" <[EMAIL PROTECTED]>:
>> With the help of Ingmar we did some cleanup and added support for
>> eclass-manpages at
>> http://git.overlays.gentoo.org/gitweb/?p=proj/desktop-effects.git;a=blob_plain;f=eclass/bzr.ecl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 5 Oct 2008 17:07:40 +0200
> Alexis Ballier <[EMAIL PROTECTED]> wrote:
>> Maybe eclasses should die on unknown eapi; the fact is I really hate
>> the current way it's done when switching an ebuild to EAPI-2 which
>> uses
> On Sun, 5 Oct 2008, Robert Buchholz wrote:
>> So if the ebuild includes non-existing files in DOCS, then why would
>> you want to suppress the warnings?
> I don't. My point was that the default action on an empty DOCS
> variable is to "dodoc AUTHORS ChangeLog NEWS README", and this
> should
On Sunday, 5. October 2008, Ulrich Mueller wrote:
> > On Sun, 5 Oct 2008, Robert Buchholz wrote:
> >> >
> >> > It's not. If you want to have default DOCS then you should loop
> >> > through the items and check with [[ -e ]] before trying to
> >> > install them.
> >>
> >> So, maybe just do a 'do
Thomas Sachau a écrit :
Why not do both (rebuild and install) with the doc useflag and none of both, if
it is not set? Imho
the doc flag is for control of installation for (additional) docs, the way it
is used for gtk-doc is
surely confusing.
Building gtk-doc documentation pulls in a lot of
> On Sun, 5 Oct 2008, Robert Buchholz wrote:
>> > It's not. If you want to have default DOCS then you should loop
>> > through the items and check with [[ -e ]] before trying to
>> > install them.
>> So, maybe just do a 'dodoc "${DOCS}"' and omit the die? Then it won't
>> fail but the warning
On Sun, 5 Oct 2008 17:38:11 +0200
Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> > By the way, do we really want to special case eapi-2 in every
> > eclass ? That's lot of code duplication and will get even worse
> > when we'll reach eapi-42. That would have been cool to have a pm
> > function that te
> On Sun, 5 Oct 2008, Alexis Ballier wrote:
> Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
>> Export it if and only if EAPI is 2.
> By the way, do we really want to special case eapi-2 in every eclass ?
> That's lot of code duplication and will get even worse when we'll reach
> eapi-42. That wo
On Sun, 5 Oct 2008 17:07:40 +0200
Alexis Ballier <[EMAIL PROTECTED]> wrote:
> Maybe eclasses should die on unknown eapi; the fact is I really hate
> the current way it's done when switching an ebuild to EAPI-2 which
> uses an eclass that exports src_compile; most eclasses don't special
> case eapi-
Thomas Sachau <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
excerpted below, on Sun, 05 Oct 2008 14:24:55 +0200:
> I just had a user in bugzilla who thought, the developer profile would
> be for software developers, not just for gentoo developers. Probably he
> is not the only one.
>
> What abou
On Sun, 5 Oct 2008 15:24:20 +0100
Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> On Sun, 5 Oct 2008 16:15:46 +0200
> Alexis Ballier <[EMAIL PROTECTED]> wrote:
> > An eapi.eclass with such functions and lists of eapi & features
> > maintained there could help though.
>
> The problem is, 'features' c
On Sun, 5 Oct 2008 16:15:46 +0200
Alexis Ballier <[EMAIL PROTECTED]> wrote:
> An eapi.eclass with such functions and lists of eapi & features
> maintained there could help though.
The problem is, 'features' change between EAPIs. For example, all three
EAPIs have src_compile, but it does different
On Sun, 5 Oct 2008 15:07:27 +0100
Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> On Sun, 5 Oct 2008 15:36:30 +0200
> Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> > How should exporting of src_configure in eclasses be handled? Should
> > it be conditional, depending on the EAPI? Or is it O.K. to expor
On Sunday, 5. October 2008, Ulrich Mueller wrote:
> > On Tue, 30 Sep 2008, Petteri Räty wrote:
> >>>
> >>> dodoc ${DOCS} || die "dodoc failed"
> >>
> >> This seems alright fine to me
> >
> > It's not. If you want to have default DOCS then you should loop
> > through the items and check with [[
On Sun, 5 Oct 2008 15:36:30 +0200
Ulrich Mueller <[EMAIL PROTECTED]> wrote:
> How should exporting of src_configure in eclasses be handled? Should
> it be conditional, depending on the EAPI? Or is it O.K. to export
> src_configure unconditionally, since it doesn't harm for EAPI<2?
Export it if and
How should exporting of src_configure in eclasses be handled? Should
it be conditional, depending on the EAPI? Or is it O.K. to export
src_configure unconditionally, since it doesn't harm for EAPI<2?
A concrete example is elisp.eclass which should export an empty
elisp_src_configure function for E
Petteri Räty schrieb:
> Currently the doc use flag on gtk-doc using packages does not control
> doc installation but instead whether to rebuild them so that they are
> properly cross linked. I think we should be using a separate use flag
> from doc for this purpose. Any comments?
>
> 15:40 <@Betel
Currently the doc use flag on gtk-doc using packages does not control
doc installation but instead whether to rebuild them so that they are
properly cross linked. I think we should be using a separate use flag
from doc for this purpose. Any comments?
15:40 <@Betelgeuse> EvaSDK: Just change the doc
I just had a user in bugzilla who thought, the developer profile would be for
software developers,
not just for gentoo developers. Probably he is not the only one.
What about either adding some big warning on portage output or renaming this
profile to e.g.
"gentoodeveloper"?
--
Thomas Sachau
On Sunday 05 of October 2008 12:44:20 Robin H. Johnson wrote:
> I'm in favour of allowing the variable to empty, because I'm a lazy
> upstream, and I haven't even made a basic webpage for some of my
> projects (diradm, localshell, readahead-list, etc).
lol
+1 for allowing empty $HOMEPAGE
For projects where the upstream has vanished off the face of the planet,
and the project was reasonably obscure, but the code works fine still,
there's problems with either the requirements of HOMEPAGE or the repoman
check.
From PMS:
\item[HOMEPAGE] The URI or URIs for a package's homepage, inclu
> On Tue, 30 Sep 2008, Petteri Räty wrote:
>>> dodoc ${DOCS} || die "dodoc failed"
>> This seems alright fine to me
> It's not. If you want to have default DOCS then you should loop
> through the items and check with [[ -e ]] before trying to install
> them.
I'm not convinced that this is a
53 matches
Mail list logo
