On 25 July 2012 02:52, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote:
While I completely understand where Fabian is coming from on all this I
respectfully disagree. Long term gentoo users do NOT read the handbook,
ever. I still install new systems with odd hacks that I picked up when
On Tue, Jul 24, 2012 at 01:15:43PM -0400, Michael Orlitzky wrote:
I think a news item is reasonable here (in addition to the above). Most
users don't know about the move from /etc/make.conf to
/etc/portage/make.conf. After this change, there will be a
gradually-increasing need to know that a
Sven Vermeulen posted on Wed, 25 Jul 2012 08:05:02 + as excerpted:
On Tue, Jul 24, 2012 at 01:15:43PM -0400, Michael Orlitzky wrote:
I think a news item is reasonable here (in addition to the above). Most
users don't know about the move from /etc/make.conf to
/etc/portage/make.conf. After
On Tue, 2012-07-24 at 20:55 -0400, Walter Dnes wrote:
On Tue, Jul 24, 2012 at 11:42:31AM +0200, Ralph Sennhauser wrote
man 5 portage about files in /etc/portage
make.conf
The global custom settings for Portage. See make.conf(5). If
present, this file will over??? ride
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/24/2012 04:30 PM, W. Trevor King wrote:
Hmm, are the manuals versioned with a public interface (git clone
…/handbook.git)? That would make finding new gems in the manual
much easier.
Yes, yes they are.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/24/2012 04:19 PM, Michael Mol wrote:
Another user opinion...it would be a significant improvement to
the stage images and live discs to include the latest copy of the
handbook, so that a network connection isn't required to access
it. But
On Wed, Jul 25, 2012 at 9:25 AM, Aaron W. Swenson titanof...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/24/2012 04:19 PM, Michael Mol wrote:
Another user opinion...it would be a significant improvement to
the stage images and live discs to include the latest copy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/07/12 05:13 PM, Brian Harring wrote:
On Tue, Jul 24, 2012 at 04:32:00PM -0400, Michael Mol wrote:
I've often seen cases like these handled by keeping a referenced
file where it's traditionally expected to be found, but leaving a
comment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/07/12 08:55 PM, Walter Dnes wrote:
On Tue, Jul 24, 2012 at 11:42:31AM +0200, Ralph Sennhauser wrote
man 5 portage about files in /etc/portage
make.conf The global custom settings for Portage. See
make.conf(5). If present, this file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25-07-2012 13:29, Michael Mol wrote:
On Wed, Jul 25, 2012 at 9:25 AM, Aaron W. Swenson
titanof...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
On 07/24/2012 04:19 PM, Michael Mol wrote:
Another user opinion...it would
On Wed, Jul 25, 2012 at 10:27 AM, Jorge Manuel B. S. Vicetto
jmbsvice...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25-07-2012 13:29, Michael Mol wrote:
On Wed, Jul 25, 2012 at 9:25 AM, Aaron W. Swenson
titanof...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/25/2012 10:27 AM, Jorge Manuel B. S. Vicetto wrote:
On 25-07-2012 13:29, Michael Mol wrote:
On Wed, Jul 25, 2012 at 9:25 AM, Aaron W. Swenson
titanof...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
On 07/24/2012
On Thursday 19 July 2012 02:57:09 Ulrich Mueller wrote:
On Wed, 18 Jul 2012, Ciaran McCreesh wrote:
Many eclasses (eutils being the most prominent example) contain:
DESCRIPTION=Based on the ${ECLASS} eclass
Is this of any use?
The reason that sort of thing is there is because in
On Wednesday 18 July 2012 13:53:37 Ulrich Mueller wrote:
Our current policy [1] requires that ebuilds must assign the seven
variables DESCRIPTION, HOMEPAGE, SRC_URI, LICENSE, SLOT, KEYWORDS, and
IUSE, even if their value is empty.
Could we drop this requirement? Repoman already enforces that
On Wed, 25 Jul 2012, Mike Frysinger wrote:
Our current policy [1] requires that ebuilds must assign the seven
variables DESCRIPTION, HOMEPAGE, SRC_URI, LICENSE, SLOT, KEYWORDS,
and IUSE, even if their value is empty.
Could we drop this requirement? Repoman already enforces that
El mié, 25-07-2012 a las 18:38 +0200, Ulrich Mueller escribió:
[...]
The single exception to this is IUSE, which
is required to be present in an ebuild even if it's empty. Maybe we
should drop this requirement, too.
+1
signature.asc
Description: This is a digitally signed message part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/25/2012 12:56 PM, Pacho Ramos wrote:
El mié, 25-07-2012 a las 18:38 +0200, Ulrich Mueller escribió:
[...]
The single exception to this is IUSE, which
is required to be present in an ebuild even if it's empty. Maybe we
should drop this
On 22 July 2012 16:12, Doug Goldstein car...@gentoo.org wrote:
I've got a few ROMs to add to the tree and some which are already in
the tree if people have a suggestion where they should live. Short
list:
ipxe
openbios
seabios
sgabios
vgabios
--
Doug Goldstein
I just noticed that the
On 23 July 2012 08:48, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote:
A fair point, suggestion retracted. I'm on board with sys-firmware as
well, but I do see some advantage of the current way of putting the
firmware in the category of what it is for...
If you wanted, you could do
On Wed, 25 Jul 2012 18:38:05 +0200
Ulrich Mueller u...@gentoo.org wrote:
On Wed, 25 Jul 2012, Mike Frysinger wrote:
Our current policy [1] requires that ebuilds must assign the seven
variables DESCRIPTION, HOMEPAGE, SRC_URI, LICENSE, SLOT, KEYWORDS,
and IUSE, even if their value is
On Wednesday 25 July 2012 12:38:05 Ulrich Mueller wrote:
On Wed, 25 Jul 2012, Mike Frysinger wrote:
Our current policy [1] requires that ebuilds must assign the seven
variables DESCRIPTION, HOMEPAGE, SRC_URI, LICENSE, SLOT, KEYWORDS,
and IUSE, even if their value is empty.
Could we
On Thu, 26 Jul 2012, Kent Fredric wrote:
In short, Yay, thanks for sys-firmware, I look forward to it not
being an empty category
We could create a category metadata file. ;)
Is the following O.K.:
The sys-firmware category contains various firmware and microcode.
Ulrich
Kent Fredric schrieb:
On 23 July 2012 08:48, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote:
A fair point, suggestion retracted. I'm on board with sys-firmware as
well, but I do see some advantage of the current way of putting the
firmware in the category of what it is for...
If you
23 matches
Mail list logo
