On Wed, Mar 7, 2012 at 12:27 PM, C Anthony Risinger wrote:
>
> ... i thought you were asking a) "share a base read-only chroot", so
> you don't have to rebuild/clean it. since the base is readonly, you
> must then --bind mount (shared/persistent) or create an empty
> repository (within the overla
On Fri, Mar 2, 2012 at 6:23 PM, David C. Rankin
wrote:
> On 03/02/2012 04:48 PM, C Anthony Risinger wrote:
>> IIRC makechrootpkg used to create an overlay/union before starting,
>> which would keep your original root intact. if you put your builds on
>> a btrfs filesystem i believe makechrootpkg
On 03/02/2012 04:48 PM, C Anthony Risinger wrote:
> IIRC makechrootpkg used to create an overlay/union before starting,
> which would keep your original root intact. if you put your builds on
> a btrfs filesystem i believe makechrootpkg will snapshot the fs before
> starting (i know im mixing mkar
On Fri, Mar 2, 2012 at 4:31 PM, David C. Rankin
wrote:
>
> Guys,
>
> What is the best way to clean a chroot without doing another mkarchroot?
>
> In the chroot I have /root and /david. With Trinity there are 2 different Qt
> dependencies that can be used Qt3 and TQt3. I have built a set of packa
Guys,
What is the best way to clean a chroot without doing another mkarchroot?
In the chroot I have /root and /david. With Trinity there are 2 different Qt
dependencies that can be used Qt3 and TQt3. I have built a set of packages on
Qt3, not I want to rebuild starting with TQt3. I don't want
5 matches
Mail list logo
