Anyone else interested in starting up a herd for configuration tools?
Much of app-admin/ and probably many other packages would qualify. I'd
like to get my system-config-* stuff into a proper herd and I'm sure
many other people have packages in there for which they would like to do
the same.
Thank
In 30 days, kyro-drivers will finally leave the tree and move on to a
new life in the Attic. These binary-only drivers only work on 2.4
kernels and there's no anticipated 2.6 support that I know of.
Thanks,
Donnie
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
m h wrote:
> Other than a text editor?
>
> I'd like to have a tool that can add USE flags on a per package or
> global level. (I'm doing this in some build scripts and would prefer
> just to have a tool, rather than sed or some other shell hackery).
On Thu, 26 Oct 2006 23:12:13 +0200 Carsten Lohrke <[EMAIL PROTECTED]>
wrote:
| On Thursday 26 October 2006 22:41, Jakub Moc wrote:
| > +1 ... SPF is broken by design.
|
| Right¹. Don't understand why it gets used either.
It gets used because of klieber.
--
Ciaran McCreesh
Mail:
On Thu, 26 Oct 2006 21:43:56 +0200 Marius Mauch <[EMAIL PROTECTED]>
wrote:
| > At the risk of reopening a large can of worms, can somebody explain
| > to me why the license groups idea won't run into the same conceptual
| > issues that derailed GLEP 29 (USE groups)? Am I missing something
| > obvi
On Thu, 26 Oct 2006 21:43:56 +0200
Marius Mauch <[EMAIL PROTECTED]> wrote:
> On Thu, 26 Oct 2006 12:50:01 -0500
> Grant Goodyear <[EMAIL PROTECTED]> wrote:
>
> > Marius Mauch wrote: [Thu Oct 26 2006, 12:02:59PM CDT]
> > > Ok, as there is currently a lot of work going on for GLEP 23
> > > (licese
On Thursday 26 October 2006 22:41, Jakub Moc wrote:
> +1 ... SPF is broken by design.
Right¹. Don't understand why it gets used either.
Carsten
[1] http://homepages.tesco.net/J.deBoynePollard/FGA/smtp-spf-is-harmful.html
pgp9zuYplnFtJ.pgp
Description: PGP signature
On Thu, 2006-10-26 at 21:43 +0200, Marius Mauch wrote:
> On Thu, 26 Oct 2006 12:50:01 -0500
> Grant Goodyear <[EMAIL PROTECTED]> wrote:
>
> > Marius Mauch wrote: [Thu Oct 26 2006, 12:02:59PM CDT]
> > > Ok, as there is currently a lot of work going on for GLEP 23
> > > (licese based visibility filt
Hi!
On Thu, 26 Oct 2006, Alin Nastac wrote:
> Facts:
> a) current SPF TXT record of our domain is "v=spf1 mx ptr ?all"
> b) I use my own MTA to send my @g.o messages.
> c) Probably I am not the only one who does that
d) I've just spent nearly an hour to debug an error that resulted
f
Alin Nastac napsal(a):
> The proper TXT record for our domain would be "v=spf1 +all", which
> translates (according to http://new.openspf.org/SPF_Record_Syntax ) as
> "the domain owner thinks that SPF is useless". And it really is useless,
> at the very least for our widespread organization.
+1
Facts:
a) current SPF TXT record of our domain is "v=spf1 mx ptr ?all"
b) I use my own MTA to send my @g.o messages.
c) Probably I am not the only one who does that
I've just evaluated SPF support in spamassassin and I've discovered that
SPF_NEUTRAL has a big fat score of 1.1.
I don't
On Thu, 26 Oct 2006 12:50:01 -0500
Grant Goodyear <[EMAIL PROTECTED]> wrote:
> Marius Mauch wrote: [Thu Oct 26 2006, 12:02:59PM CDT]
> > Ok, as there is currently a lot of work going on for GLEP 23
> > (licese based visibility filtering aka ACCEPT_LICENSE) the topic of
> > license groups came up,
On Thu, 26 Oct 2006 12:08:36 -0600
"m h" <[EMAIL PROTECTED]> wrote:
> Other than a text editor?
>
> I'd like to have a tool that can add USE flags on a per package or
> global level. (I'm doing this in some build scripts and would prefer
> just to have a tool, rather than sed or some other shell
On Thu, 26 Oct 2006 10:15:56 -0700
Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> Marius Mauch wrote:
> > Ok, as there is currently a lot of work going on for GLEP 23
> > (licese based visibility filtering aka ACCEPT_LICENSE) the topic of
> > license groups came up, in particular the way how they sh
Uhoh, forgive me for not reading the other replies before writing a
completely redundant one.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Marius Mauch wrote:
> Ok, as there is currently a lot of work going on for GLEP 23
> (licese based visibility filtering aka ACCEPT_LICENSE) the topic of
> license groups came up, in particular the way how they should be
> (technically) defined.
>
> The simplest way is a line based format
>
Joshua Nichols ha scritto:
> m h wrote:
[...]
Joshua please do not cross post
/me run fast and far
--
gentoo-dev@gentoo.org mailing list
m h wrote:
> Other than a text editor?
>
> I'd like to have a tool that can add USE flags on a per package or
> global level. (I'm doing this in some build scripts and would prefer
> just to have a tool, rather than sed or some other shell hackery).
>
> I couldn't find anything via a quick search
Donnie-
thanks for the suggestion (guess I need to look through app-portage
before I post next time). I'll check out these tools (though they are
written in perl. I was thinking about using python)
-matt
On 10/26/06, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
m h wrote:
> Other than a tex
Marius Mauch wrote: [Thu Oct 26 2006, 12:02:59PM CDT]
> Ok, as there is currently a lot of work going on for GLEP 23
> (licese based visibility filtering aka ACCEPT_LICENSE) the topic of
> license groups came up, in particular the way how they should be
> (technically) defined.
>
> The simplest wa
m h wrote:
use-config --add --component sys-devel/gcc --flag fortran
(adds the fortran USE flag to package.use for gcc)
A --remove would remove the fortran USE flag, and --unset would put
"-fortran" instead. A --global would update make.conf instead of
package.use.
Add to make.conf:
flagedit
On Thu, 26 Oct 2006 20:18:40 +0200
Harald van Dijk <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 26, 2006 at 07:02:36PM +0200, Marius Mauch wrote:
> > Ok, as there is currently a lot of work going on for GLEP 23
> > (licese based visibility filtering aka ACCEPT_LICENSE) the topic of
> > license groups c
Donnie Berkholz wrote:
m h wrote:
Other than a text editor?
I'd like to have a tool that can add USE flags on a per package or
global level. (I'm doing this in some build scripts and would prefer
just to have a tool, rather than sed or some other shell hackery).
Probably enhancing uf
m h wrote:
> Other than a text editor?
>
> I'd like to have a tool that can add USE flags on a per package or
> global level. (I'm doing this in some build scripts and would prefer
> just to have a tool, rather than sed or some other shell hackery).
Probably enhancing ufed or flagedit to enable
Other than a text editor?
I'd like to have a tool that can add USE flags on a per package or
global level. (I'm doing this in some build scripts and would prefer
just to have a tool, rather than sed or some other shell hackery).
I couldn't find anything via a quick search on google.
Here's my
On Thu, Oct 26, 2006 at 07:02:36PM +0200, Marius Mauch wrote:
> Ok, as there is currently a lot of work going on for GLEP 23
> (licese based visibility filtering aka ACCEPT_LICENSE) the topic of
> license groups came up, in particular the way how they should be
> (technically) defined.
>
> The sim
Marius Mauch wrote:
> Ok, as there is currently a lot of work going on for GLEP 23
> (licese based visibility filtering aka ACCEPT_LICENSE) the topic of
> license groups came up, in particular the way how they should be
> (technically) defined.
>
> The simplest way is a line based format
>
Ok, as there is currently a lot of work going on for GLEP 23
(licese based visibility filtering aka ACCEPT_LICENSE) the topic of
license groups came up, in particular the way how they should be
(technically) defined.
The simplest way is a line based format
...
however this doesn't allow
Donnie Berkholz wrote:
Kinda makes you think they shouldn't be specific to types of plugin,
doesn't it? There could be an eselect browser-plugin module that can
select various types of browser plugins. Not sure how a 4th level would
fit in with eselect as far as usability etc goes, though.
Thank
The OSL is working on moving several of their boxes this morning at 1600
UTC to the new datacenter racks. We were planning on moving the last two
of our machines during this time, but unfortunately a scheduling
conflict came up so we'll have to do ours later next week. The bad part
of this means th
On Thu, 2006-10-26 at 13:47 +0200, Christoph Mende wrote:
> You could release the new version under the old name as a meta package
> that installs the package with the new name
Ehh... no.
You add the new package under the new name, remove the old package, and
do a package move. Denis posted the
On 10/26/06, Peter Volkov (pva) <[EMAIL PROTECTED]> wrote:
One of packages I maintain changed its name. What shall be done, so
users of the package were aware about package name change and upgraded
flawlessly?
See :
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=5#doc_ch
You could release the new version under the old name as a meta package
that installs the package with the new name
On Thu, 2006-10-26 at 14:53 +0400, Peter Volkov (pva) wrote:
> Hello.
>
> One of packages I maintain changed its name. What shall be done, so
> users of the package were aware about
Hello.
One of packages I maintain changed its name. What shall be done, so
users of the package were aware about package name change and upgraded
flawlessly?
Thank you,
Peter.
signature.asc
Description: This is a digitally signed message part
Sounds logical to me, if more than a few ebuilds are using it then making it global would probly be the way :)CpuID.On 10/26/06, Steve Dibb <
[EMAIL PROTECTED]> wrote:If no one objects, I'd like to add an mplayer global USE flag to replace all the
local ones. 5 ebuilds use it right now for all the
35 matches
Mail list logo