Hi Brian,

Various users has an individual habits. The most annoying way I can imagine is to push the prefabricated .hgignore to the gate.

Much better way seems to me to set the post-clone hook in the ~/.hgrc in the individual users directory:
----------------------------------------------------------------------------------------
[hooks]
post-clone = ( cphgign () { dir="$1" ; [ x"$1" != x ] || dir="gate" ; cd "$dir" ; echo "cloned to: `pwd`" ; cat ~/how/Userland/hgignore > .hgignore ; } ; cphgign "`echo $HG_PATS | sed -e 's/\[//;s/\]//;s/,/ /' | sed -e "s/\'//g" | sed -e 's/userland//' | sed -e 's/^[ ]*//'`")
----------------------------------------------------------------------------------------

Prerequisites are:
----------------------------------------------------------------------------------------
[paths]
...
userland=ssh://[email protected]//gates/gate
----------------------------------------------------------------------------------------
...in the ~/.hgrc

~/how/Userland/hgignore  ...user's customized "hgignore"

i.e. mine:
----------------------------------------------------------------------------------------
.hgignore

syntax: regexp
^i386/.*
^sparc/.*
^tools/.+\.(o|so)
^tools/.+\.pyc
^components/components.mk
^components/depends.mk
^components/.+/build/.*

^components/zip/zip30.*
^components/unzip/unzip60.*
^components/samba/mozldap/mozldap-6\.0\.7.*
^components/samba/samba30/samba-3\.0\.37.*
^components/samba/samba/samba-3\.6\.6.*
^components/samba/samba/samba-3\.5\.15.*
^components/cups/cups-1\.4\.5.*
^components/foomatic/filters/foomatic-filters-4\.0\.15.*
^components/foomatic/db/foomatic-db-20080903.*
^components/foomatic/fppd/foomatic-filters-ppds-20080818.*
^components/foomatic/db-engine/foomatic-db-engine-3\.0-20080903.*
^samba/.*
^webrev/.*
^fix-cups/.*
^foomatic/.*

syntax: glob
*.tar
*.tar.gz
*.tar.bz2
*.zip
*.tgz
nohup.out
----------------------------------------------------------------------------------------
...is customized for Samba and printing

As a subject of discussion for improvement is to push i.e. userland-hgignore-base into the gate and individual users can modify their post-clone to do i.e.:

cat userland-hgignore-base ~/how/Userland/hgignore-cust > .hgignore

...which can be subject of CR 7119950 integration

Jiri


On 06/14/12 06:23 PM, [email protected] wrote:
Please Review the new comment logged against CI4651
     7119950 Userland gate needs a .hgignore file.
         http://monaco.us.oracle.com/detail.jsp?cr=7119950

https://rpetools.uk.oracle.com/citool/CI4651/

2012-06-14 17:23:12 Europe/London [[email protected]]
Hi,

To check that the hgignore does not ignore anything you can clone fresh 
workspace and do
hg status -I

I tried that and that is clean now.

But I wonder, should not we build full workspace and add any things which are 
missed by the generic rules?

Also the file could contain hints how to test that your modified .hgignore is 
correct (hg status -I on fresh workspace and hg status being clean on full 
build).
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss

Reply via email to