Jon Portnoy | 1 Jul 11:40 2003
Picon

Broken emerge sync

Yes, we know 'emerge sync' is currently borked. It's being worked on.

--

-- 
Jon Portnoy
avenj/irc.freenode.net

--
gentoo-dev <at> gentoo.org mailing list

Patrick Kursawe | 1 Jul 11:46 2003
Picon

for those who don't want to wait for "emerge sync" to be fixed...

"emerge regen" seems to fix it locally, if you desperately want to
emerge something.

Bye, Patrick
Seemant Kulleen | 1 Jul 11:58 2003
Picon

Interest Check: Dynamic config files for portage

Hi All,

Before I go and invalidate a bug, I thought I might take the idea around here to see if it has any merit in terms
of usefulness/interest.

The idea stems from the fact that etc-updating a make.conf file can be a bit of a stressful event.  And as
portage's set of features grows, so too will the size of the make.conf file.  I get the impression that the
make.conf file is a little hard to parse, with the huge comment blocks etc etc.  So my proposal is this: a
make.conf.d directory which contains files for each section of the make.conf: use, flags, fetch,
packagevars.  That way, USE flags can be explained and specified in use, compiler flags in the flags file,
fetch will contain the fetchcommands, mirrors (both distfiles and rsync), and packagevars can contain
things like ALSA_CARDS for those of us on 2.4 kernels, and VIDEO_CARDS for those of us who have
xfree/xfree-drm/whatever-future-windowing-system-we-add, and so on.  This way, the actual
make.conf file (which tends to be about 10 lines of uncommented items in the usual case) can be dynamically
generated from the information in those files.

Anyway, it's not an urgent issue by any means, but a thought.

Ciao,

--

-- 
Seemant Kulleen
Developer and Project Co-ordinator,
Gentoo Linux					http://www.gentoo.org/~seemant

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E
Rigo Ketelings | 1 Jul 12:35 2003
Picon

Re: Interest Check: Dynamic config files for portage

Op di 01-07-2003, om 11:58 schreef Seemant Kulleen:
> Hi All,
> 
> Before I go and invalidate a bug, I thought I might take the idea around here to see if it has any merit in terms
of usefulness/interest.
> 

Like the idea, not the name ;)....Is there anything against make.d ?

> The idea stems from the fact that etc-updating a make.conf file can be a bit of a stressful event.  And as
portage's set of features grows, so too will the size of the make.conf file.  I get the impression that the
make.conf file is a little hard to parse, with the huge comment blocks etc etc.  So my proposal is this: a
make.conf.d directory which contains files for each section of the make.conf: use, flags, fetch,
packagevars.  That way, USE flags can be explained and specified in use, compiler flags in the flags file,
fetch will contain the fetchcommands, mirrors (both distfiles and rsync), and packagevars can contain
things like ALSA_CARDS for those of us on 2.4 kernels, and VIDEO_CARDS for those of us who have
xfree/xfree-drm/whatever-future-windowing-system-we-add, and so on.  This way, the actual
make.conf file (which tends to be about 10 lines of uncommented items in the usual case) can be dynamically
generated from the information in those files.
> 
> Anyway, it's not an urgent issue by any means, but a thought.
> 
> Ciao,

Rogi

--
gentoo-dev <at> gentoo.org mailing list

(Continue reading)

sf | 1 Jul 12:46 2003
Picon

Re: Interest Check: Dynamic config files for portage

Seemant Kulleen wrote:
> Hi All,
> 
> Before I go and invalidate a bug, I thought I might take the idea around here to see if it has any merit in terms
of usefulness/interest.
> 
> The idea stems from the fact that etc-updating a make.conf file can be a bit of a stressful event.  And as
portage's set of features grows, so too will the size of the make.conf file.  I get the impression that the
make.conf file is a little hard to parse, with the huge comment blocks etc etc.  So my proposal is this: a
make.conf.d directory which contains files for each section of the make.conf: use, flags, fetch,
packagevars.  That way, USE flags can be explained and specified in use, compiler flags in the flags file,
fetch will contain the fetchcommands, mirrors (both distfiles and rsync), and packagevars can contain
things like ALSA_CARDS for those of us on 2.4 kernels, and VIDEO_CARDS for those of us who have
xfree/xfree-drm/whatever-future-windowing-system-we-add, and so on.  This way, the actual
make.conf file (which tends to be about 10 lines of uncommented items in the usual case) can be dynamically
generated from the information in those files.
> 
> Anyway, it's not an urgent issue by any means, but a thought.
> 
> Ciao,
> 

Why not leave make.conf alone and put the comments into make.globals?

--
gentoo-dev <at> gentoo.org mailing list

Jon Portnoy | 1 Jul 12:49 2003
Picon

Cancel that - rsync fixed

Thanks to robbat2, rsync issues are fixed.

--

-- 
Jon Portnoy
avenj/irc.freenode.net

--
gentoo-dev <at> gentoo.org mailing list

Ferris McCormick | 1 Jul 12:32 2003

Re: Interest Check: Dynamic config files for portage

On Tue, 1 Jul 2003, Seemant Kulleen wrote:

> Hi All,
> 
> Before I go and invalidate a bug, I thought I might take the idea around here to see if it has any merit in terms
of usefulness/interest.
> 
> The idea stems from the fact that etc-updating a make.conf file can be a bit of a stressful event.  And as
portage's set of features grows, so too will the size of the make.conf file.  I get the impression that the
make.conf file is a little hard to parse, with the huge comment blocks etc etc.  So my proposal is this: a
make.conf.d directory which contains files for each section of the make.conf: use, flags, fetch,
packagevars.  That way, USE flags can be explained and specified in use, compiler flags in the flags file,
fetch will contain the fetchcommands, mirrors (both distfiles and rsync), and packagevars can contain
things like ALSA_CARDS for those of us on 2.4 kernels, and VIDEO_CARDS for those of us who have
xfree/xfree-drm/whatever-future-windowing-system-we-add, and so on.  This way, the actual
make.conf file (which tends to be about 10 lines of uncommented items in the usual case) can be dynamically
generated from the information in those files.
> 
> Anyway, it's not an urgent issue by any means, but a thought.
>
I like the idea.

 
> Ciao,
> 
> -- 
> Seemant Kulleen
> Developer and Project Co-ordinator,
> Gentoo Linux					http://www.gentoo.org/~seemant
> 
(Continue reading)

Svyatogor | 1 Jul 16:49 2003
Picon

Re: Interest Check: Dynamic config files for portage

On Tue, 1 Jul 2003 02:58:24 -0700
Seemant Kulleen <seemant <at> gentoo.org> wrote:

> Hi All,
> 
> Before I go and invalidate a bug, I thought I might take the idea around here
> to see if it has any merit in terms of usefulness/interest.
> 
> The idea stems from the fact that etc-updating a make.conf file can be a bit
> of a stressful event.  And as portage's set of features grows, so too will the
> size of the make.conf file.  I get the impression that the make.conf file is a
> little hard to parse, with the huge comment blocks etc etc.  So my proposal is
> this: a make.conf.d directory which contains files for each section of the
> make.conf: use, flags, fetch, packagevars.  That way, USE flags can be
> explained and specified in use, compiler flags in the flags file, fetch will
> contain the fetchcommands, mirrors (both distfiles and rsync), and packagevars
> can contain things like ALSA_CARDS for those of us on 2.4 kernels, and
> VIDEO_CARDS for those of us who have
> xfree/xfree-drm/whatever-future-windowing-system-we-add, and so on.  This way,
> the actual make.conf file (which tends to be about 10 lines of uncommented
> items in the usual case) can be dynamically generated from the information in
> those files.
> 

Nice idea. Why not? It should make the make.conf easier to manage and easier to
update.

--

-- 
Sergey Kuleshov <svyatogor <at> gentoo.org>
Let the Force be with us!
(Continue reading)

Stuart Herbert | 1 Jul 13:12 2003
Picon
Picon

RE: Cancel that - rsync fixed

Not quite ... just ran 'emerge rsync' and receieved warnings about syntax
errors in dev_php/php-4.3.2-r1.ebuild and dev_php/mod_php-4.3.2-r3.ebuild.

FYI

> -----Original Message-----
> From: Jon Portnoy [mailto:avenj <at> gentoo.org] 
> Sent: 01 July 2003 11:50
> To: gentoo-dev <at> gentoo.org
> Subject: [gentoo-dev] Cancel that - rsync fixed
> 
> 
> Thanks to robbat2, rsync issues are fixed.
> 
> -- 
> Jon Portnoy
> avenj/irc.freenode.net
> 
> --
> gentoo-dev <at> gentoo.org mailing list
> 
> 

--
gentoo-dev <at> gentoo.org mailing list

Dan Armak | 1 Jul 13:16 2003
Picon

Make mad use flag global

Hi all,

The mad use flag which enables use of the media-sound/mad mpeg decoder is 
currently local to the app-games/scummvm package. kde-base/arts (in its cvs 
state anyway) can also optionally use mad - right now the dep is always 
enabled. Other packages will likely make use of the flag in the future. I 
propose to make the mad use flag global and use it in the arts ebuild, and 
will do so unless someone objects.

--

-- 
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://cvs.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951

Gmane