HEX

File: //usr/lib/python3/dist-packages/hgext/__pycache__/sparse.cpython-310.pyc
o

�]Lb�9�@s�dZddlmZddlmZddlmZddlmZm	Z	m
Z
mZmZm
Z
mZmZmZmZmZmZdZiZe�e�Zdd�Zd	d
�Zdd�Zd
d�Zdd�Zdd�Zdd�Zedddged�ed�fddged�ed�fddged�ed�fd d!d"ed#�fd$d%ged&�ed�fd$d'ged(�ed�fd$d)ged*�ed�fd$d+d"ed,�fd$d-d"ed.�fd$d/d"ed0�fg
e	j ed1�d2d3�d4d5��Z!d6S)7aG	allow sparse checkouts of the working directory (EXPERIMENTAL)

(This extension is not yet protected by backwards compatibility
guarantees. Any aspect may break in future releases until this
notice is removed.)

This extension allows the working directory to only consist of a
subset of files for the revision. This allows specific files or
directories to be explicitly included or excluded. Many repository
operations have performance proportional to the number of files in
the working directory. So only realizing a subset of files in the
working directory can improve performance.

Sparse Config Files
-------------------

The set of files that are part of a sparse checkout are defined by
a sparse config file. The file defines 3 things: includes (files to
include in the sparse checkout), excludes (files to exclude from the
sparse checkout), and profiles (links to other config files).

The file format is newline delimited. Empty lines and lines beginning
with ``#`` are ignored.

Lines beginning with ``%include `` denote another sparse config file
to include. e.g. ``%include tests.sparse``. The filename is relative
to the repository root.

The special lines ``[include]`` and ``[exclude]`` denote the section
for includes and excludes that follow, respectively. It is illegal to
have ``[include]`` after ``[exclude]``.

Non-special lines resemble file patterns to be added to either includes
or excludes. The syntax of these lines is documented by :hg:`help patterns`.
Patterns are interpreted as ``glob:`` by default and match against the
root of the repository.

Exclusion patterns take precedence over inclusion patterns. So even
if a file is explicitly included, an ``[exclude]`` entry can remove it.

For example, say you have a repository with 3 directories, ``frontend/``,
``backend/``, and ``tools/``. ``frontend/`` and ``backend/`` correspond
to different projects and it is uncommon for someone working on one
to need the files for the other. But ``tools/`` contains files shared
between both projects. Your sparse config files may resemble::

  # frontend.sparse
  frontend/**
  tools/**

  # backend.sparse
  backend/**
  tools/**

Say the backend grows in size. Or there's a directory with thousands
of files you wish to exclude. You can modify the profile to exclude
certain files::

  [include]
  backend/**
  tools/**

  [exclude]
  tools/tests/**
�)�absolute_import)�_)�setattr)�cmdutil�commands�dirstate�error�
extensions�
logcmdutil�match�merge�pycompat�	registrar�sparse�utilsships-with-hg-corecCs*dt_t|�t|�t|�t|�dS)NT)r�enabled�_setupclone�	_setuplog�	_setupadd�_setupdirstate)�ui�r�./usr/lib/python3/dist-packages/hgext/sparse.py�extsetupgs
rcCsp|}t|�sJ�|tur(||jvr|j|}t||||��n	|jd}|tus|tur6ttd�||f��dS)ziReplace a filecache property with a new class. This allows changing the
    cache invalidation condition.rstype '%s' has no property '%s'N)�callable�object�__dict__r�	__bases__�AttributeErrorr)�cls�propname�replacement�origcls�origrrr�replacefilecacheps


���r$cCs2tjd}|d�d�dd�}t�td|�dS)Nslog|history�)��sparseNs1limit to changesets affecting the sparse checkoutcs<|�|�}|j�d�rt������fdd�}|�|�}|S)Nr'cs"�|}t�fdd�|��D��S)Nc3s�|]	}�|�r|VqdS�Nr��.0�f)�sparsematchrr�	<genexpr>�s�zD_setuplog.<locals>._initialrevs.<locals>.ctxmatch.<locals>.<genexpr>)�any�files)�rev�ctx��repor,rr�ctxmatch�sz1_setuplog.<locals>._initialrevs.<locals>.ctxmatch)�opts�getr�matcher�filter)r#r3�wopts�revsr4rr2r�_initialrevs�s


z_setuplog.<locals>._initialrevss_initialrevs)r�table�appendr	�wrapfunctionr
)r�entryr;rrrr�s
�	rcsn|�d��|�d��|�d��|�d�}|s+�s�s�r+���fdd�}t�td|�|||g|�Ri|��S)N�include�exclude�enable_profile�narrowcs4tj|����i���dd�||g|�Ri|��S)NT)r@rA�
enableprofile�usereporootpaths)r�updateconfigr3�
unfiltered)r#r1�args�kwargs�rDrAr@rr�clonesparse�s
�z$_clonesparsecmd.<locals>.clonesparsesupdate)r6r	r>�mergemod)r#rr3rHr5�
narrow_patrKrrJr�_clonesparsecmd�s



rNcCs`tjd}|d�ddgdf�|d�ddgdf�|d�ddgd	f�t�tjdt�dS)
Nscloner%r&�enable-profilesenable a sparse profile�includesinclude sparse pattern�excludesexclude sparse pattern)rr<r=r	�wrapcommandrN)rr?rrrr�s

rcCs4tjd}|d�d�dd�}t�tjd|�dS)Nsaddr%)�sr'Ns8also include directories of added files in sparse configc	_s^|�d�r#t�}|D]}t�|�\}}|�|�q
tj||t|�d�|||g|�Ri|��S)Nr)r@)r6�setr�split�addrrF�list)	r#rr3�patsr5�dirs�pat�dirname�basenamerrr�_add�s
z_setupadd.<locals>._add)rr<r=r	rR)rr?r]rrrr�s
�		rcsnd
dd�}t�tjd|�ddd�}t�tjd|�gd	�}td
��|D]}�fdd�}t�tj||�q$dS)z|Modify the dirstate to prevent stat'ing excluded files,
    and to prevent modifications to files outside the checkout.
    Tc	Ss<t�|���}t�|j|g�}t�||�}|||||||�Sr()�matchmod�exactr/�unionmatcher�_sparsematcher�intersectmatchers)	r#�selfr�subrepos�unknown�ignored�full�em�smrrr�walk�sz_setupdirstate.<locals>.walkswalkNcsh|j����s-�fdd�|D�}|r�fdd�|D�}|dur-�fdd�|D�}|�|�}|||||�S)Nc�g|]}�|�r|�qSrrr)�r7rr�
<listcomp>��z4_setupdirstate.<locals>._rebuild.<locals>.<listcomp>crkrrr)rlrrrm�rncsh|]}�|�s|�qSrrr)rlrr�	<setcomp>�rnz3_setupdirstate.<locals>._rebuild.<locals>.<setcomp>)ra�always�union)r#rc�parent�allfiles�changedfiles�dirstatefilestoremoverrlr�_rebuild�s
z _setupdirstate.<locals>._rebuildsrebuild)sset_trackeds
set_untrackedscopyswinclude file with `hg debugsparse --include <pattern>` or use `hg add -s <file>` to include file directory while addingcs\|j}|��s#|D]}|dur"||�s"||vr"tjtd�|�d��q	||g|�Ri|��S)Ns3cannot add '%s' - it is outside the sparse checkout��hint)rarpr�Abortr)r#rcrHrIr,r+rwrr�_wrappers����z _setupdirstate.<locals>._wrapper)Tr()r	r>rr)rrjrv�	editfuncs�funcrzrrwrr�s

��rsdebugsparse�IrPs$include files in the sparse checkoutsPATTERN�XrQs$exclude files in the sparse checkout�d�deletesdelete an include/exclude rule�f�forceFs.allow changing rules even with pending changesr&rOsenables the specified profilesdisable-profilesdisables the specified profilesimport-rulessimports rules from a filesclear-ruless"clears local include/exclude rules�refreshs,updates the working after sparseness changes�resetsmakes the repo full agains
[--OPTION]T)�	helpbasiccKs�t�|�}|�d�}|�d�}|�d�}|�d�}|�d�}|�d�}|�d�}	|�d�}
|�d	�}|�d
�}t�|ddd	�}
t|pK|pK|
pK|pK|pK|�}t|t|
�g�}|dkr`t�t	d���|d
kr�|j
�d�r�|�|j
�
d�d�t�|�}|r�|�t	d��|�d�|�d�dSt�t	d���|r�tj||||||
|||d�	|r�tj||||d�|	r�tj||d�|r�z,|��}tttj||��t�|�|d��}tj|||d
|d|dd�W|��dS|��wdS)a�make the current checkout sparse, or edit the existing checkout

    The sparse command is used to make the current checkout sparse.
    This means files that don't meet the sparse condition will not be
    written to disk, or show up in any working copy operations. It does
    not affect files in history in any way.

    Passing no arguments prints the currently applied sparse rules.

    --include and --exclude are used to add and remove files from the sparse
    checkout. The effects of adding an include or exclude rule are applied
    immediately. If applying the new rule would cause a file with pending
    changes to be added or removed, the command will fail. Pass --force to
    force a rule change even with pending changes (the changes on disk will
    be preserved).

    --delete removes an existing include/exclude rule. The effects are
    immediate.

    --refresh refreshes the files on disk based on the sparse rules. This is
    only necessary if .hg/sparse was changed by hand.

    --enable-profile and --disable-profile accept a path to a .hgsparse file.
    This allows defining sparse checkouts and tracking them inside the
    repository. This is useful for defining commonly used sparse checkouts for
    many people to use. As the profile definition changes over time, the sparse
    checkout will automatically be updated appropriately, depending on which
    changeset is checked out. Changes to .hgsparse are not applied until they
    have been committed.

    --import-rules accepts a path to a file containing rules in the .hgsparse
    format, allowing you to add --include, --exclude and --enable-profile rules
    in bulk. Like the --include, --exclude and --enable-profile switches, the
    changes are applied immediately.

    --clear-rules removes all local include and exclude rules, while leaving
    any enabled profiles in place.

    Returns 0 if editing the sparse checkout succeeds.
    rPrQr�senable_profilesdisable_profilesimport_rulessclear_rulesr�r�r�r%stoo many flags specifiedrr'�
s/Temporarily Included Files (for merge/rebase):
Ns@the debugsparse command is only supported on sparse repositories)r@rA�reset�deleterD�disableprofile�force)r��)�added�dropped�conflicting)r
�byteskwargsr6r�check_at_most_one_arg�bool�sumrryr�vfs�exists�status�readr�readtemporaryincludes�joinrF�importfromfiles�
clearrules�wlock�map�len�refreshwdirr7�printchanges�release)rr3r5r@rAr�rDr��importrulesr�r��refreshr��actionrF�count�temporaryincludesr��fcountsrrr�debugsparses�
i









��
��������r�N)"�__doc__�
__future__r�mercurial.i18nr�mercurial.pycompatr�	mercurialrrrrr	r
rr^rrLr
rrr�
testedwith�cmdtable�commandrr$rrNrrr�templateoptsr�rrrr�<module>s�B8
	?���������:�;�@