Hi all,
I want to make a live-ebuild for a private subversion repository.
I see in the developers manual [1] that CVS have the vars ECVS_USER and
ECVS_PASS, but cannot found equivalent ones for SVN [2].
Anyone knows what would be the prefered way to do that? Is safe to
include the login in the eb
On Tue, Jan 25, 2011 at 05:11:56PM -0600, Ryan Hill wrote:
> sys-libs/timezone-data
> most of app-doc (ie. anything installing just docs or text)
>
> I'd also like permission to stabilize fonts ourselves once they've cleared
> amd64 and x86.
>
>
> --
> fonts, gcc-porting, it m
On Mon, 24 Jan 2011 13:31:20 +0100, Christian Faulhammer wrote:
Hi,
over the course of the years the x86 (and other architectures as
well)
has given away permissions to maintainers/teams to mark packages
stable themselves. As there never was a definitive list what
exceptions exist, I compiled
On Thu, 27 Jan 2011 10:19:51 -0600
Jeremy Olexa wrote:
> Probably OT, sorry. Isn't it time we gained this concept of "noarch"
> for packages that only install text files or packages that don't
> compile anything...
No, since there's no such thing as an app that's guaranteed to be
portable.
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 27.1.2011 17:30, Ciaran McCreesh napsal(a):
> On Thu, 27 Jan 2011 10:19:51 -0600
> Jeremy Olexa wrote:
>> Probably OT, sorry. Isn't it time we gained this concept of "noarch"
>> for packages that only install text files or packages that don't
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 27 Jan 2011 17:48:54 +0100
Tomáš Chvátal wrote:
> Dne 27.1.2011 17:30, Ciaran McCreesh napsal(a):
> > On Thu, 27 Jan 2011 10:19:51 -0600
> > Jeremy Olexa wrote:
> >> Probably OT, sorry. Isn't it time we gained this concept of
> >> "noarch" f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 27 Jan 2011 17:48:54 +0100
Tomáš Chvátal wrote:
> Dne 27.1.2011 17:30, Ciaran McCreesh napsal(a):
> > On Thu, 27 Jan 2011 10:19:51 -0600
> > Jeremy Olexa wrote:
> >> Probably OT, sorry. Isn't it time we gained this concept of
> >> "noarch"
Hi,
The accessibility team has permission to mark some app-accessibility
packages stable because they require specialized hardware:
app-accessibility/brltty
app-accessibility/speakup (this one will become moot when linux 2.6.37
goes stable)
Just to clarify, we are talking only about the x86 arch
On Thu, Jan 27, 2011 at 9:16 AM, Natanael Olaiz wrote:
> Hi all,
>
> I want to make a live-ebuild for a private subversion repository.
> I see in the developers manual [1] that CVS have the vars ECVS_USER and
> ECVS_PASS, but cannot found equivalent ones for SVN [2].
>
> Anyone knows what would b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok bad example on the posix-sh file. But anyway even you can check what
stuff the thing does and decide upon it. Anyway even tho you nitpick on
something you don't need to.
There is at minimal the binary files example where you just place them
somewher
Hi,
William Hubbs :
> Just to clarify, we are talking only about the x86 architecture right?
At the moment yes. On the exceptions page I linked there are some
conditions under which you can stabilise yourself after permission is
granted:
* The prerequisites of stabilisation policy still apply.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 27 Jan 2011 18:07:30 +0100
Tomáš Chvátal wrote:
> Ok bad example on the posix-sh file. But anyway even you can check
> what stuff the thing does and decide upon it. Anyway even tho you
> nitpick on something you don't need to.
> There is at mi
On 01/27/2011 09:05 AM, Matthew Summers wrote:
> Now, as to whether to include the value ESVN_PASSWORD in the ebuild, I would
> not do that. Personally, I would setup svn+ssh and use an ssh key to access
> the repo. I do this with git using the git eclass. I am prompted for a
> password/key by port
On 01/27/2011 05:30 PM, Ciaran McCreesh wrote:
> No, since there's no such thing as an app that's guaranteed to be
> portable.
What about app-doc/php-doc? Yeah, single use case. But I feel stupid
requesting keywords for it. It's all text.
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 27.1.2011 18:16, Ciaran McCreesh napsal(a):
> On Thu, 27 Jan 2011 18:07:30 +0100
> Tomáa Chvátal wrote:
>> Ok bad example on the posix-sh file. But anyway even you can check
>> what stuff the thing does and decide upon it. Anyway even tho you
>> n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 27 Jan 2011 18:59:53 +0100
Tomáš Chvátal wrote:
> If depgraph is to be found broken for such architecture it is
> shadowed (or treated as without keywords, whatever we find to like in
> our implementation in package manager) and not permitted
On 01/27/2011 06:59 PM, Tomáš Chvátal wrote:
> Adding ebuilds with noarch keyword must be preceded with:
> All ebuilds seeking to have this feature implemented must be discussed
> on #gentoo-dev mailing list and proven not having portability issues.
So instead of opening a bug for all arches, I po
Tomáš Chvátal posted on Thu, 27 Jan 2011 18:59:53 +0100 as excerpted:
> If ebuild contains ~noarch in KEYWORDS it is not permitted to contain
> anything else.
/If/ we're going to go this route, at least noarch plus -arch, so archs
can at least opt-out.
--
Duncan - List replies preferred. No
On Thu, 27 Jan 2011 18:27:57 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:
> Tomáš Chvátal posted on Thu, 27 Jan 2011 18:59:53 +0100 as excerpted:
> > If ebuild contains ~noarch in KEYWORDS it is not permitted to
> > contain anything else.
>
> /If/ we're going to go this route, at least noarch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 27.1.2011 19:09, Matti Bickel napsal(a):
> On 01/27/2011 06:59 PM, Tomáš Chvátal wrote:
>> Adding ebuilds with noarch keyword must be preceded with:
>> All ebuilds seeking to have this feature implemented must be discussed
>> on #gentoo-dev mailing
Ciaran McCreesh posted on Thu, 27 Jan 2011 18:36:59 + as excerpted:
> On Thu, 27 Jan 2011 18:27:57 + (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>> Tomáš Chvátal posted on Thu, 27 Jan 2011 18:59:53 +0100 as excerpted:
>> > If ebuild contains ~noarch in KEYWORDS it is not permitted to cont
On Thu, Jan 27, 2011 at 11:24 AM, Zac Medico wrote:
> On 01/27/2011 09:05 AM, Matthew Summers wrote:
> > Now, as to whether to include the value ESVN_PASSWORD in the ebuild, I
> would
> > not do that. Personally, I would setup svn+ssh and use an ssh key to
> access
> > the repo. I do this with gi
On 01/27/2011 11:08 AM, Matthew Summers wrote:
> One question though. Since the 'portage' user has its $home set by default
> to /var/tmp/portage how would you recommend handling the ssh key situation
> since that directory is somewhat special?
Well, I've never tried it, so I don't have any recomm
On 01/27/2011 07:42 PM, Tomáš Chvátal wrote:
> Only to gain the ~allarch. When it gains it gets tested by arch member
> of any team and stabled. Verstanden? :)
Yep, I think I did. But what if introduce, say, a non-portable find
command into a new revision that breaks on some arches. I'll carry ove
On Thu, 27 Jan 2011 16:30:12 +
Ciaran McCreesh wrote:
> On Thu, 27 Jan 2011 10:19:51 -0600
> Jeremy Olexa wrote:
> > Probably OT, sorry. Isn't it time we gained this concept of "noarch"
> > for packages that only install text files or packages that don't
> > compile anything...
>
> No, s
Arch teams handle KEYWORDREQ bugs too.
I have masked the only dev-lang/perl version keyworded for "sparc-fbsd"
3 weeks ago. No user, no dev complained by now (#288028).
So I think this arch (as much as amd64-fbsd) is unsupported/dead but
repoman's dependencies check reports a lot of warnings due
26 matches
Mail list logo
