> On Wed, 19 Dec 2012, Brian Dolbec wrote:
> just to clarify, I'm voting for...
> /var/cache/distfiles
> /var/cache/packages
Fine.
> /var/cache/repositories/
> /var/cache/repositories/gentoo <== the main portage tree
> /var/cache/repositories/local<== the new location for a local over
On Thu, 20 Dec 2012 00:27:26 +0100
"J. Roeleveld" wrote:
> On Wednesday, December 19, 2012 09:13:28 AM Greg KH wrote:
> > On Tue, Dec 18, 2012 at 08:21:36AM +0100, J. Roeleveld wrote:
> > > On Mon, December 17, 2012 22:31, Greg KH wrote:
> > > > On Mon, Dec 17, 2012 at 09:03:40PM +0100, J. Roelev
Ulrich Mueller posted on Thu, 20 Dec 2012 09:11:39 +0100 as excerpted:
> Also I wonder if local overlays should be in /var/cache? It might not
> always be possible to restore them.
Good point. My local overlay's in /usr/local/ (which is a dedicated
partition I actually keep several backups of,
On Thursday 20 December 2012 09:11:39 Ulrich Mueller wrote:
> > /var/cache/repositories/local<== the new location for a local overlay
>
> Also I wonder if local overlays should be in /var/cache? It might not
> always be possible to restore them.
So, this is the present /usr/local/portage? What
On 12/20/2012 03:31 AM, Michał Górny wrote:
> On Thu, 20 Dec 2012 00:27:26 +0100
> "J. Roeleveld" wrote:
>
>> On Wednesday, December 19, 2012 09:13:28 AM Greg KH wrote:
>>> On Tue, Dec 18, 2012 at 08:21:36AM +0100, J. Roeleveld wrote:
On Mon, December 17, 2012 22:31, Greg KH wrote:
> On
On Wed, 19 Dec 2012 14:19:52 -0800
Zac Medico wrote:
> On 12/19/2012 02:01 PM, Alan McKinnon wrote:
> > On Wed, 19 Dec 2012 14:56:44 +0100
> > Diego Elio Pettenò wrote:
> >
> >> Just mv /usr/portage /var/portage ? FFS no. Among other things, as
> >> many said before, we should really take distf
On Thu, Dec 20, 2012 at 4:25 AM, George Shapovalov wrote:
> On Thursday 20 December 2012 09:11:39 Ulrich Mueller wrote:
>> > /var/cache/repositories/local<== the new location for a local overlay
>>
>> Also I wonder if local overlays should be in /var/cache? It might not
>> always be possible t
On Thu, Dec 20, 2012 at 6:21 AM, Richard Yao wrote:
> No one has proposed moving everything to /usr. At the minimum, we would
> still have /etc and /var in /, as well as various mountpoints. If we do
> move those to /usr, then we effectively renamed / to /usr, which is
> pointless. The absurdity o
On 12/20/2012 07:02 AM, Rich Freeman wrote:
> On Thu, Dec 20, 2012 at 6:21 AM, Richard Yao wrote:
>> No one has proposed moving everything to /usr. At the minimum, we would
>> still have /etc and /var in /, as well as various mountpoints. If we do
>> move those to /usr, then we effectively renamed
> On Thu, 20 Dec 2012, Rich Freeman wrote:
> I actually like the /var/cache/repositories approach. You can always
> add a symlink to it if you want to for convenience (as I already do
> for /var/lib/portage/world). There is really nothing special about
> /usr/portage, other than it being the
Zac Medico writes:
> On 12/19/2012 02:01 PM, Alan McKinnon wrote:
>> If we are going to move distfiles out of the tree into, what are the
>> odds of getting /some/path/portage/local to move somewhere else too?
>
> What program uses this "local" directory? It's not used directly by
> portage itsel
On Thu, 2012-12-20 at 09:11 +0100, Ulrich Mueller wrote:
> > On Wed, 19 Dec 2012, Brian Dolbec wrote:
>
> > just to clarify, I'm voting for...
>
> > /var/cache/distfiles
> > /var/cache/packages
>
> Fine.
>
> > /var/cache/repositories/
> > /var/cache/repositories/gentoo <== the main portag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/12/12 10:37 AM, Brian Dolbec wrote:
>>
>>> /var/cache/repositories/ /var/cache/repositories/gentoo <==
>>> the main portage tree /var/cache/repositories/local<== the
>>> new location for a local overlay
>>> /var/cache/repositories/some-
On Thu, Dec 20, 2012 at 11:01 AM, Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 20/12/12 10:37 AM, Brian Dolbec wrote:
>>>
/var/cache/repositories/ /var/cache/repositories/gentoo <==
the main portage tree /var/cache/repositories/local<== the
>>>
On 20/12/2012 17:16, Michael Mol wrote:
>
> /var/cache/portage/distfiles
> /var/cache/portage/repositories/gentoo
> /var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
> /var/db/portage/repositories/{non-cache,repo,names,go,here}
+1
--
Diego Elio Pettenò — Flameeyes
flamee
On Thu, Dec 20, 2012 at 11:19 AM, Diego Elio Pettenò
wrote:
> On 20/12/2012 17:16, Michael Mol wrote:
>>
>> /var/cache/portage/distfiles
>> /var/cache/portage/repositories/gentoo
>> /var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
>> /var/db/portage/repositories/{non-cache
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/20/2012 11:16 AM, Michael Mol wrote:
> On Thu, Dec 20, 2012 at 11:01 AM, Ian Stakenvicius wrote:
> On 20/12/12 10:37 AM, Brian Dolbec wrote:
>
>> /var/cache/repositories/ /var/cache/repositories/gentoo <==
>> the main portage tree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/12/12 11:25 AM, Rick "Zero_Chaos" Farina wrote:
> On 12/20/2012 11:16 AM, Michael Mol wrote:
>> On Thu, Dec 20, 2012 at 11:01 AM, Ian Stakenvicius
>> wrote: On 20/12/12 10:37 AM, Brian Dolbec
>> wrote:
>>
>>> /var/cache/repositories/
> On Thu, 20 Dec 2012, Diego Elio Pettenò wrote:
>> /var/cache/portage/distfiles
>> /var/cache/portage/repositories/gentoo
>> /var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
>> /var/db/portage/repositories/{non-cache,repo,names,go,here}
> +1
-1
The subdirs are too
On Thu, Dec 20, 2012 at 12:05 PM, Ulrich Mueller wrote:
>> On Thu, 20 Dec 2012, Diego Elio Pettenň wrote:
>
>>> /var/cache/portage/distfiles
>>> /var/cache/portage/repositories/gentoo
>>> /var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
>>> /var/db/portage/repositories
The FHS says:
/var/cache is intended for cached data from applications. Such data
is locally generated as a result of time-consuming I/O or
calculation. The application must be able to regenerate or restore
the data.
Now I wonder: After removal of e.g. the Portage tree from a system,
On Thu, Dec 20, 2012 at 06:58:11AM -0500, Rich Freeman wrote:
> On Thu, Dec 20, 2012 at 4:25 AM, George Shapovalov wrote:
> > On Thursday 20 December 2012 09:11:39 Ulrich Mueller wrote:
> >> > /var/cache/repositories/local<== the new location for a local overlay
> >>
> >> Also I wonder if loca
> On Thu, 20 Dec 2012, Michael Mol wrote:
/var/cache/portage/distfiles
/var/cache/portage/repositories/gentoo
/var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
/var/db/portage/repositories/{non-cache,repo,names,go,here}
>> -1
>>
>> The subdirs are
/var/cache/portage/distfiles
/var/cache/portage/repositories/gentoo
/var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
/var/db/portage/repositories/{non-cache,repo,names,go,here}
+1
-1
The subdirs are too deeply nested.
There is a practical advantage of having the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/12/12 12:27 PM, Ulrich Mueller wrote:
> The FHS says:
>
> /var/cache is intended for cached data from applications. Such
> data is locally generated as a result of time-consuming I/O or
> calculation. The application must be able to regenerat
On Thu, 20 Dec 2012 07:37:52 -0800
Brian Dolbec wrote:
> My idea for having all repos under one directory is to make it easier
> for a pkg manager to simply scan the directory to know all installed
> overlays.
That's going to cause trouble, unless we start forcing overlays to
contain enough infor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/12/12 12:52 PM, Vaeth wrote:
>
> However, I have strong objections against using /var/cache at all:
> FHS explicitly states:
>
> "Such data is locally generated ... The application must be able
> to regenerate or restore the data."
>
emerg
On Thu, 2012-12-20 at 18:27 +0100, Ulrich Mueller wrote:
> The FHS says:
>
>/var/cache is intended for cached data from applications. Such data
>is locally generated as a result of time-consuming I/O or
>calculation. The application must be able to regenerate or restore
>the data.
> On Thu, 20 Dec 2012, Ian Stakenvicius wrote:
> On 20/12/12 12:27 PM, Ulrich Mueller wrote:
>> The FHS says:
>>
>> /var/cache is intended for cached data from applications. Such
>> data is locally generated as a result of time-consuming I/O or
>> calculation. The application must be able to
On Thu, 20 Dec 2012 18:27:26 +0100
Ulrich Mueller wrote:
> The FHS says:
>
>/var/cache is intended for cached data from applications. Such data
>is locally generated as a result of time-consuming I/O or
>calculation. The application must be able to regenerate or restore
>the data.
On Thursday 20 December 2012 13:36:27 Alan McKinnon wrote:
> > What program uses this "local" directory? It's not used directly by
> > portage itself, though portage has an exclude for it in the default
> > PORTAGE_RSYNC_OPTS setting
> > (in /usr/share/portage/config/make.globals).
>
> It goes bac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/12/12 01:12 PM, Ulrich Mueller wrote:
>
> What about /usr/portage/licenses, for example? Some of the
> licenses are required to be present on the system if the
> corresponding software is installed. So users cannot legally remove
> them.
>
.
On 20 December 2012 17:44, Ulrich Mueller wrote:
>> On Thu, 20 Dec 2012, Michael Mol wrote:
>
> /var/cache/portage/distfiles
> /var/cache/portage/repositories/gentoo
> /var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
> /var/db/portage/repositories/{non-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/12/12 01:18 PM, George Shapovalov wrote:
> On Thursday 20 December 2012 13:36:27 Alan McKinnon wrote:
>>> What program uses this "local" directory? It's not used
>>> directly by portage itself, though portage has an exclude for
>>> it in the de
On Thu, 20 Dec 2012 18:44:06 +0100
Ulrich Mueller wrote:
> There's no good reason for nesting it so deeply. As it is proposed
> above, /var/cache/portage would contain only two subdirectories, and
> /var/cache/portage/repositories only a single "gentoo" on a stable
> system. Also /var/cache itself
On 20/12/2012 19:19, Ian Stakenvicius wrote:
> ... well, along those lines, the list of licenses are not pertinent
> to the system unless the software that relates to them is installed;
> maybe emerge should automatically during the merge phase ensure the
> license files are copied to the main sys
On Thu, Dec 20, 2012 at 12:31 PM, William Hubbs wrote:
> On Thu, Dec 20, 2012 at 06:58:11AM -0500, Rich Freeman wrote:
>> On Thu, Dec 20, 2012 at 4:25 AM, George Shapovalov wrote:
>> > On Thursday 20 December 2012 09:11:39 Ulrich Mueller wrote:
>> >> > /var/cache/repositories/local<== the new
Ciaran McCreesh wrote:
> On Thu, 20 Dec 2012 18:44:06 +0100
> Ulrich Mueller wrote:
>> There's no good reason for nesting it so deeply. As it is proposed
>> above, /var/cache/portage would contain only two subdirectories, and
>> /var/cache/portage/repositories only a single "gentoo" on a stable
>>
> On Thu, 20 Dec 2012, Ciaran McCreesh wrote:
>> We should go with a shorter (easier to remember, easier to type) path
>> and move things at least one level up. Two would be even better.
> You shouldn't ever be typing that path in...
Ebuilds tell users to do so:
pkg_nofetch() {
einfo "P
On Thursday 20 December 2012 13:21:11 Ian Stakenvicius wrote:
> > Nope, he means /usr/portage/local, not /usr/local/portage.
>
> Alan's description *was* for /usr/portage/local
Really? It matches /usr/local/portage pretty well. How did it come around
then? We had /usr/local/portage for ages for s
On 12/20/2012 06:12 AM, Graham Murray wrote:
> Zac Medico writes:
>
>> On 12/19/2012 02:01 PM, Alan McKinnon wrote:
>>> If we are going to move distfiles out of the tree into, what are the
>>> odds of getting /some/path/portage/local to move somewhere else too?
>>
>> What program uses this "local
Ian Stakenvicius wrote:
"Such data is locally generated ... The application must be able
to regenerate or restore the data."
emerge --sync <-- regenerates/restores the portage tree
Perhaps my English is too poor, but IMHO
download != regenerate/restore.
Indeed, the FHS also emphasizes only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/12/12 01:55 PM, George Shapovalov wrote:
> On Thursday 20 December 2012 13:21:11 Ian Stakenvicius wrote:
>>> Nope, he means /usr/portage/local, not /usr/local/portage.
>>
>> Alan's description *was* for /usr/portage/local
> Really? It matches
On 12/20/2012 03:36 AM, Alan McKinnon wrote:
> On Wed, 19 Dec 2012 14:19:52 -0800
> Zac Medico wrote:
>
>> On 12/19/2012 02:01 PM, Alan McKinnon wrote:
>>> On Wed, 19 Dec 2012 14:56:44 +0100
>>> Diego Elio Pettenò wrote:
>>>
Just mv /usr/portage /var/portage ? FFS no. Among other things, as
On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico wrote:
> On 12/18/2012 11:58 PM, Duncan wrote:
>> I didn't know that. Last I knew, stable portage had special-case
>> acceptance of @system and @world to prepare the way, but I hadn't seen
>> that full /etc/portage/sets/* and /var/lib/portage/world_sets
On 12/20/2012 12:09 PM, Rich Freeman wrote:
> On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico wrote:
>> On 12/18/2012 11:58 PM, Duncan wrote:
>>> I didn't know that. Last I knew, stable portage had special-case
>>> acceptance of @system and @world to prepare the way, but I hadn't seen
>>> that full /
On Thu, Dec 20, 2012 at 1:19 PM, Ian Stakenvicius wrote:
> On 20/12/12 01:12 PM, Ulrich Mueller wrote:
>>
>> What about /usr/portage/licenses, for example? Some of the
>> licenses are required to be present on the system if the
>> corresponding software is installed. So users cannot legally remove
On Thu, 20 Dec 2012 19:18:56 +0100
George Shapovalov wrote:
> > It goes back a long time, and is basically a poor man's local
> > overlay without having to use layman. As I understand it, portage
> > will treat the directory like any other when looking for ebuilds
> > and resolving deps, but excl
El jue, 20-12-2012 a las 12:23 -0800, Zac Medico escribió:
> On 12/20/2012 12:09 PM, Rich Freeman wrote:
> > On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico wrote:
> >> On 12/18/2012 11:58 PM, Duncan wrote:
> >>> I didn't know that. Last I knew, stable portage had special-case
> >>> acceptance of @sy
On 12/20/2012 10:19 AM, Ian Stakenvicius wrote:
> On 20/12/12 01:12 PM, Ulrich Mueller wrote:
>
>> What about /usr/portage/licenses, for example? Some of the
>> licenses are required to be present on the system if the
>> corresponding software is installed. So users cannot legally remove
>> them.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/20/2012 03:25 PM, Rich Freeman wrote:
> On Thu, Dec 20, 2012 at 1:19 PM, Ian Stakenvicius wrote:
>> On 20/12/12 01:12 PM, Ulrich Mueller wrote:
>>>
>>> What about /usr/portage/licenses, for example? Some of the
>>> licenses are required to be pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/20/2012 01:14 PM, Ciaran McCreesh wrote:
> On Thu, 20 Dec 2012 18:27:26 +0100
> Ulrich Mueller wrote:
>> The FHS says:
>>
>>/var/cache is intended for cached data from applications. Such data
>>is locally generated as a result of time-co
On 12/20/2012 12:35 PM, Pacho Ramos wrote:
> El jue, 20-12-2012 a las 12:23 -0800, Zac Medico escribió:
>> On 12/20/2012 12:09 PM, Rich Freeman wrote:
>>> On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico wrote:
On 12/18/2012 11:58 PM, Duncan wrote:
> I didn't know that. Last I knew, stable po
> We're drifting here, but the concept is that machine-local stuff like
> configuration stays out of /usr, and generic distro stuff stays in
> /usr.
>
> A webserver for site1 vs site2 would be identical in /usr, but
> different elsewhere.
That has always been the case. In fact people have tried t
On Thu, Dec 20, 2012 at 3:46 PM, Zac Medico wrote:
>
> If only a small subset of licenses require it, then maybe we should just
> use dodoc on those licenses that require it. Saving all licenses could
> be overkill.
Seems like a reasonable compromise. I would think such licenses would
be rare.
After talking with Mike, sks is now up for grabs, feel free to take it
Thanks
signature.asc
Description: This is a digitally signed message part
On Thu, 20 Dec 2012 19:44:36 +0100
Ulrich Mueller wrote:
> > On Thu, 20 Dec 2012, Ciaran McCreesh wrote:
> >> We should go with a shorter (easier to remember, easier to type)
> >> path and move things at least one level up. Two would be even
> >> better.
>
> > You shouldn't ever be typing tha
Due araujo no longer taking care of them:
dev-lang/gnu-smalltalk
dev-lang/gwydion-dylan-bin
dev-lang/pike
dev-lang/io
signature.asc
Description: This is a digitally signed message part
On Thu, 20 Dec 2012 15:09:45 -0500
Rich Freeman wrote:
> On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico
> wrote:
> > On 12/18/2012 11:58 PM, Duncan wrote:
> >> I didn't know that. Last I knew, stable portage had special-case
> >> acceptance of @system and @world to prepare the way, but I hadn't
> >
Ulrich Mueller schrieb:
>> Now I wonder: After removal of e.g. the Portage tree from a system,
>> it is generally not possible to restore it. (It can be refetched,
>> but not to its previous state.)
Is it required that the _exact_ _same_ _data_ will be regenerated? This
is not the case with most u
> On Thu, 20 Dec 2012, Rich Freeman wrote:
>> If only a small subset of licenses require it, then maybe we should just
>> use dodoc on those licenses that require it. Saving all licenses could
>> be overkill.
> Seems like a reasonable compromise. I would think such licenses would
> be rare.
sorry for the format, this was
Sent from my iPhone
On 2012-12-20, at 4:51 PM, Ciaran McCreesh
wrote:
> On Thu, 20 Dec 2012 15:09:45 -0500
> Rich Freeman wrote:
>> On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico
>> wrote:
>>> On 12/18/2012 11:58 PM, Duncan wrote:
I didn't know that. Last I
On 12/20/2012 03:00 PM, Ian Stakenvicius wrote:
>
>
> sorry for the format, this was
> Sent from my iPhone
>
> On 2012-12-20, at 4:51 PM, Ciaran McCreesh
> wrote:
>
>> On Thu, 20 Dec 2012 15:09:45 -0500
>> Rich Freeman wrote:
>>> On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico
>>> wrote:
O
On Mon, Dec 17, 2012 at 01:16:25PM -0800, Greg KH wrote:
> On a personal note, if any copyright assignment was in place, I would
> never have been able to become a Gentoo developer, and if it were to be
> put into place, I do not think that I would be allowed to continue to be
> one. I'm sure lots
I'm curious who had the brain dead idea to retire Gentoo developers
that are still interested in the distro, that maintain low activity
packages for herds that are stretched way too thin, and are still
contributing to the distro in many ways other than direct CVS commits
(e.g. overlays, user suppor
Doug Goldstein wrote:
> I'm really just trying to understand the sense in this.
I guess that it's a bias. Everyone wants active developers.
One way to achieve that is to retire anyone who isn't active.
I would prefer another approach, but I also understand that Gentoo
has had massive people issu
On Thu, Dec 20, 2012 at 10:21 PM, Doug Goldstein wrote:
> I could MAYBE understand it if they're consuming some valuable
> resource that we need to free up by retiring them. But instead they
> get a nasty-gram about their impending retirement and decide if that's
> how they are to be treated that
On Thu, Dec 20, 2012 at 7:21 PM, Doug Goldstein wrote:
> I'm curious who had the brain dead idea to retire Gentoo developers
> that are still interested in the distro, that maintain low activity
> packages for herds that are stretched way too thin, and are still
> contributing to the distro in man
On 20 December 2012 16:52, Pacho Ramos wrote:
> Due araujo no longer taking care of them:
> dev-lang/pike
I've got this one :)
On Fri, Dec 21, 2012 at 02:32:25AM +, Robin H. Johnson wrote:
> On Mon, Dec 17, 2012 at 01:16:25PM -0800, Greg KH wrote:
> > On a personal note, if any copyright assignment was in place, I would
> > never have been able to become a Gentoo developer, and if it were to be
> > put into place, I do
Rich Freeman wrote:
> I think the bar for keeping access should be kept low - they
> shouldn't be forced to go find some trivial change to make just
> to get their name in the logs.
When I first started looking into becoming a Gentoo developer I got a
very strong and very clear impression that thi
Peter Stuge wrote:
> > I think the bar for keeping access should be kept low - they
> > shouldn't be forced to go find some trivial change to make just
> > to get their name in the logs.
>
> When I first started looking into becoming a Gentoo developer I got a
> very strong and very clear impressi
On Thu, Dec 20, 2012 at 11:08 PM, Greg KH wrote:
> On Fri, Dec 21, 2012 at 02:32:25AM +, Robin H. Johnson wrote:
>> 1. Are you party to any *copyright assignment* (eg FSF copyright assignment)?
>
> You need to rephrase this to be (in order for it to make any sense):
> Are you party to any *c
On 12/20/12 7:21 PM, Doug Goldstein wrote:
> I'm curious who had the brain dead idea to retire Gentoo developers
> that are still interested in the distro, that maintain low activity
> packages for herds that are stretched way too thin, and are still
> contributing to the distro in many ways other
Rich Freeman posted on Thu, 20 Dec 2012 22:33:55 -0500 as excerpted:
> On Thu, Dec 20, 2012 at 10:21 PM, Doug Goldstein
> wrote:
>> I could MAYBE understand it if they're consuming some valuable resource
>> that we need to free up by retiring them. But instead they get a
>> nasty-gram about their
On Thu, Dec 20, 2012 at 10:09 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>
Do you realize that you just wrote a two-and-a-half page single-spaced
thousand-word email? Seriously, this is way too much. This mailing
list is way too much.
Alexandre Rostovtsev posted on Thu, 20 Dec 2012 13:10:38 -0500 as
excerpted:
> On Thu, 2012-12-20 at 18:27 +0100, Ulrich Mueller wrote:
>> The FHS says:
>>
>>/var/cache is intended for cached data from applications. Such data
>>is locally generated as a result of time-consuming I/O or
>>
Matt Turner posted on Thu, 20 Dec 2012 22:29:09 -0800 as excerpted:
> On Thu, Dec 20, 2012 at 10:09 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>>
>>
> Do you realize that you just wrote a two-and-a-half page single-spaced
> thousand-word email? Seriously, this is way too much. This mailing list
> is
> On Fri, 21 Dec 2012, Duncan wrote:
>>> The FHS says:
>>>
>>>/var/cache is intended for cached data from applications. Such
>>>data is locally generated as a result of time-consuming I/O or
>>>calculation. The application must be able to regenerate or
>>>restore the data.
>
79 matches
Mail list logo
