В Пнд, 12/11/2007 в 18:20 -0800, Donnie Berkholz пишет:
> On 00:03 Tue 13 Nov , Michael Hanselmann wrote:
> > On Mon, Nov 12, 2007 at 02:09:33PM -0800, Donnie Berkholz wrote:
> > > On 21:47 Mon 12 Nov , Michael Hanselmann (hansmi) wrote:
> > > > pkg_postinst() {
> > > > chown -R in
On 00:03 Tue 13 Nov , Michael Hanselmann wrote:
> On Mon, Nov 12, 2007 at 02:09:33PM -0800, Donnie Berkholz wrote:
> > On 21:47 Mon 12 Nov , Michael Hanselmann (hansmi) wrote:
> > > pkg_postinst() {
> > > chown -R inspircd:inspircd "${ROOT}"/etc/${PN}
> > > chmod 700 "${ROOT}"/etc/${PN}
Steve Long wrote:
>>> Whatever. Requiring root for certain tasks has a long history:
>> On the kernel side.
>>
> Hmm, I'm sure I've used several apps which required root over the years.
They are flawed unless they are things like su/sudo/... . As a fine
example about why is this checking bad, see
Donnie Berkholz wrote:
>> if [[ -n "${ver}" ]] && [[ ${ver//[a-zA-Z-]} != "${PV//[a-zA-Z]}" ]] ;
>> then
>
> It isn't terribly likely to become an issue here, but it might be nicer
> to use [[:alpha:]] than [a-zA-Z].
Is [[:alpha:]] locale-safe?
Cheers.
-jkt
--
cd /local/pub && more beer
Petteri Räty kirjoitti:
> Petteri Räty kirjoitti:
>> Usually it's best that ebuild variables follow the order that is in
>> skel.ebuild. So know we should decide where to place EAPI. I suggest we
>> put it it after LICENSE as that's where the more technical stuff like
>> SLOT starts. Attached a pat
Petteri Räty kirjoitti:
> Usually it's best that ebuild variables follow the order that is in
> skel.ebuild. So know we should decide where to place EAPI. I suggest we
> put it it after LICENSE as that's where the more technical stuff like
> SLOT starts. Attached a patch for skel.ebuild.
>
> Regar
On Mon, Nov 12, 2007 at 02:09:33PM -0800, Donnie Berkholz wrote:
> On 21:47 Mon 12 Nov , Michael Hanselmann (hansmi) wrote:
> > pkg_postinst() {
> > chown -R inspircd:inspircd "${ROOT}"/etc/${PN}
> > chmod 700 "${ROOT}"/etc/${PN}
> > chown -R inspircd:inspircd "${ROOT}"/var/log/${P
On 21:47 Mon 12 Nov , Michael Hanselmann (hansmi) wrote:
> 1.1 net-irc/inspircd/inspircd-1.1.14.ebuild
>
> file :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-irc/inspircd/inspircd-1.1.14.ebuild?rev=1.1&view=markup
> plain:
> http://sources.gentoo.org/viewcvs.py/gen
Attached are the packages masked for removal this week.
--
looks like christmas at fifty-five degrees
this latitude weakens my knees
EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 (0xF9A40662)
dev-db/firebird-docs Will
On Mon, 12 Nov 2007 12:57:06 +0100
Christian Faulhammer <[EMAIL PROTECTED]> wrote:
> Alexis Ballier <[EMAIL PROTECTED]>:
>
> > Is it possible/wanted to do that automagically for every ebuild ?
> > Like adding it to portage env variables. Or should it be done in
> > each ebuild that needs it ?
>
On Mon, Nov 12, 2007 at 01:26:46PM +0100, Marijn Schouten (hkBst) wrote:
> Ciaran McCreesh wrote:
> > On Fri, 9 Nov 2007 22:40:08 +
> > Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> >> Is the following set sufficient? Is the following set the least
> >> restrictive correct solution?
> >
> > ...
On Monday 12 of November 2007 13:26:46 Marijn Schouten (hkBst) wrote:
> What exactly is the difference between this valid situation and the
> previous invalid one?
between | | are things that can be done in parallel.
invalid:
a_pkg_setup b_pkg_setup a_build b_build | a_merge | b_merge
valid:
a_p
On Mon, Nov 12, 2007 at 09:13:32AM +, Steve Long wrote:
> > And why do you feel the need to comment when you don't know what the
> > eselect die implementation is or how the changes to it introduced in
> > Paludis make it better?
> >
> As stated, I was sharing knowledge and pointing out improv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Fri, 9 Nov 2007 22:40:08 +
> Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
>> Is the following set sufficient? Is the following set the least
>> restrictive correct solution?
>
> ... to explain the implications of these...
Alexis Ballier <[EMAIL PROTECTED]>:
> Is it possible/wanted to do that automagically for every ebuild ? Like
> adding it to portage env variables. Or should it be done in each
> ebuild that needs it ?
Those ebuilds surely inherit a TeX/LaTeX related eclass, maybe add it
there.
> And of course,
Ciaran McCreesh wrote:
> On Sun, 11 Nov 2007 09:43:49 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> > Which is just as bad.
>> >
>> No, it's better for the reason given: it doesn't require login as
>> root.
>
> And it's still checking the wrong thing.
>
Be that as it may, if a scriptwriter is c
On 10:57 Thu 18 Oct , Caleb Tennis (caleb) wrote:
> 1.1 dev-libs/libevent/libevent-1.3e.ebuild
>
> file :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libevent/libevent-1.3e.ebuild?rev=1.1&view=markup
> plain:
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/d
On 08:58 Mon 12 Nov , Aniruddha wrote:
> I am interested in resurrecting the 'seeds' project (
> http://www.gentoo.org/proj/en/seeds/ ). I first heard from it when I
> announced my stage 4 project (
> http://forums.gentoo.org/viewtopic-t-610904-highlight-.html ).
> It's is important to know th
Hi,
I am interested in resurrecting the 'seeds' project (
http://www.gentoo.org/proj/en/seeds/ ). I first heard from it when I
announced my stage 4 project (
http://forums.gentoo.org/viewtopic-t-610904-highlight-.html ).
It's is important to know that it is my intention to stay as close as
possib
19 matches
Mail list logo
