DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=DLJWAA6
	tljMikCpri0d4O6VSKrJp3fb5H+o1yeFChdCuYZs69vuiF5uahX/EtpjjfGk6r7u
	td21gm1oQL1+Cr8PIB10+IKSzX8RWLst6dKGZ872iM55YQNMN+qlrBAKUR2KTNtE
	uaYJBxBNXqhV17Wq3sItiuwg/urTRYBwFMXU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <alpine.LNX.2.00.1611101615380.6490@ming.fruitbat.org>
References: <000801d23b23$8912a3c0$9b37eb40$@bonhard.uklinux.net> <166a2465-cffb-3b15-30be-d696be8ead8e@SystematicSw.ab.ca> <alpine.LNX.2.00.1611101016260.6490@ming.fruitbat.org> <CACoZoo3A2O9owPhsAjJA1a8qZzAv83uD9gBeCksZMtDQnBrv7w@mail.gmail.com> <alpine.LNX.2.00.1611101615380.6490@ming.fruitbat.org>
From: Erik Soderquist <ErikSoderquist@gmail.com>
Date: Thu, 10 Nov 2016 20:03:58 -0500
Message-ID: <CACoZoo3Z410g_jJFOjKyUR8G+ZjBySHi-cs4V7oxcqsS9aZb2Q@mail.gmail.com>
Subject: Re: Complaining after fair notice of dropping XP support. Was: Not very nice at all.
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

On Thu, Nov 10, 2016 at 7:38 PM, Peter A. Castro wrote:
> Greetings, Erik,
>
> A good magician never reveals how the trick works.  8^)
>
> Sadly I'm not a good magician.
>
> It's not all that complicated, if you think about it.  Each time a new
> setup.ini is generated only a hand full of packages was actually updated, so
> really, day-to-day, there's not all that much change.
>
> I keep a delta database and each time I grab a new setup.ini I compare all
> of the packages listed to my existing database.  Anything new, I pull down
> and add to the archive.  Anything already present I don't re-pull.  Think of
> it as de-duplication on a package level (though I do this for more than just
> setup.ini, but that's a separate trick).
>
> It's only if you decide you want a complete copy of all packages for any
> given circa that the amount of data instantiating is alot.
>
> Then, from the setup.ini, I create a new circa directory and, really, the
> smoke-and-mirrors of the trick is that it's all symlinks to the real package
> storage, of which I have exactly one copy.  Hence, 500Gb instead of 535Tb.
>
> So, um, "Ta-da"! :-)
>
> Oh, this is all automated, btw.  I hardly touch it except to clean out old
> logs and do backups from time to time.
>
> Sorry, it wasn't all that good a trick, was it.

The automation details are primarily what I'm after, though it could
have been something like ZFS with deduplication turned on

I'm wondering if I could apply your automations to a few background
projects I'm working on

Would also be interesting to see how cleanly the existing setup could
be mirrored knowing the details of the automation... rsync would
happily copy the symlinks, and once created, a Time Machine mirror
*should* be able to "stay in sync" with the original time machine by
pulling from the cygwin main sources in the same manner.


-- Erik

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple