Mirrors
/
gparted
mirror of https://gitlab.gnome.org/GNOME/gparted.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gparted/.gitignore

60 lines
809 B
Plaintext
Raw Normal View History

Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
# List of file patterns for git to ignore.
#
# Please try to keep entries in alphabetical order :-)
#
*~
*.a
*.gmo
Add building of Google Test libraries (#781978) This closely follows the minimal-gtest-autotools template project. https://github.com/octol/minimal-gtest-autotools Now 'make check' will additionally build the Google Test C++ test framework libraries. Bug 781978 - Add Google Test C++ test framework
2017-04-20 11:44:41 -06:00
*.lo
Add *.mo to .gitignore file
2012-11-30 13:13:54 -07:00
*.mo
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
*.o
Add use of new GNOME 3 yelp-tools documentation infrastructure (!24) Second part is to use yelp-tools to build and install the documentation. Have to rename the help Manual from help/C/gparted.xml to help/C/index.docbook in accordance with this note from the GNOME Goal: Port to New Documentation Infrastructure [1]: IMPORTANT: If this is for a DocBook document, the top-level DocBook file MUST be renamed to index.docbook. Do a "git mv" and include index.docbook in HELP_FILES. Commits from gucharmap [4] and totem [5], projects which have DocBook documentation, making this same change are also useful references. [1] GNOME Goal: Port To New Documentation Infrastructure https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure [2] Yelp > Yelp Tools > yelp.m4 http://yelp.io/tools/yelp.m4.html [3] GNOME application developement overview / User help / Set up your build system https://developer.gnome.org/platform-overview/stable/dev-help-build.html.en [4] gucharmap commit "Port to new documentation infrastructure" https://gitlab.gnome.org/GNOME/gucharmap/commit/3e1526c0568f0b395fce68f9d9e09431dfcaef35 [5] totem commit "Use new documentation infrastructure" https://gitlab.gnome.org/GNOME/totem/commit/59a6bd6064fe7dd047f7b61642aba73e0ba72acf Closes !24 - Port to GNOME 3 yelp-tools documentation infrastructure
2019-02-23 03:39:57 -07:00
*.stamp
Add entries used by eclipse projects
2009-04-22 15:53:07 -06:00
.cproject
Add .csettings to .gitignore
2011-05-31 11:26:29 -06:00
.csettings
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
.deps
Add .dirstamp to .gitignore Automake build of libraries creates .dirstamp files. First added by this commit: 81b104928b35d46faf200dc3265ac2254b6246c5 Add building of Google Test libraries (#781978) Mark .dirstamp as to be ignored by GIT.
2017-08-21 01:14:11 -06:00
.dirstamp
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
.intltool-merge-cache
Remove old .cvsignore files As the source code is managed in GIT and there is a .gitignore file in the top level directory specifying file names to exclude from version control, then the old per-directory .cvsignore files for CVS are redundant. Add the only missing and applicable entry from src/.cvsignore of '.libs' to .gitignore and remove all the .cvsignore files.
2017-04-12 09:12:11 -06:00
.libs
Add entries used by eclipse projects
2009-04-22 15:53:07 -06:00
.project
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
.xml2po.mo
INSTALL
Makefile
Makefile.in
Makefile.in.in
POTFILES
aclocal.m4
autom4te.cache
.gitignore: Do not track compile script Automake 1.14 also now always creates the 'compile' script. http://git.savannah.gnu.org/cgit/automake.git/tree/NEWS?h=v1.14#n110
2018-07-30 02:23:05 -06:00
compile
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
config.*
configure
depcomp
Make .gitignore gparted* mask more specific (#587065)
2009-07-04 09:29:16 -06:00
gparted
Add an AppData file (#709164) For more information on AppData see: AppData Specification http://people.freedesktop.org/~hughsient/appdata/ Application metadata with AppData http://lwn.net/Articles/569034/ Bug #709164 - Please include an AppData file
2013-10-01 02:09:42 -06:00
gparted.appdata.xml
Make .gitignore gparted* mask more specific (#587065)
2009-07-04 09:29:16 -06:00
gparted.desktop
gparted.desktop.in
gpartedbin
Add use of new GNOME 3 yelp-tools documentation infrastructure (!24) Second part is to use yelp-tools to build and install the documentation. Have to rename the help Manual from help/C/gparted.xml to help/C/index.docbook in accordance with this note from the GNOME Goal: Port to New Documentation Infrastructure [1]: IMPORTANT: If this is for a DocBook document, the top-level DocBook file MUST be renamed to index.docbook. Do a "git mv" and include index.docbook in HELP_FILES. Commits from gucharmap [4] and totem [5], projects which have DocBook documentation, making this same change are also useful references. [1] GNOME Goal: Port To New Documentation Infrastructure https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure [2] Yelp > Yelp Tools > yelp.m4 http://yelp.io/tools/yelp.m4.html [3] GNOME application developement overview / User help / Set up your build system https://developer.gnome.org/platform-overview/stable/dev-help-build.html.en [4] gucharmap commit "Port to new documentation infrastructure" https://gitlab.gnome.org/GNOME/gucharmap/commit/3e1526c0568f0b395fce68f9d9e09431dfcaef35 [5] totem commit "Use new documentation infrastructure" https://gitlab.gnome.org/GNOME/totem/commit/59a6bd6064fe7dd047f7b61642aba73e0ba72acf Closes !24 - Port to GNOME 3 yelp-tools documentation infrastructure
2019-02-23 03:39:57 -07:00
index.docbook
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
install-sh
intltool-*
Add building of Google Test libraries (#781978) This closely follows the minimal-gtest-autotools template project. https://github.com/octol/minimal-gtest-autotools Now 'make check' will additionally build the Google Test C++ test framework libraries. Bug 781978 - Add Google Test C++ test framework
2017-04-20 11:44:41 -06:00
lib/gtest/lib
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
libtool
ltmain.sh
Include local copy of Autoconf Archive macro AX_CXX_COMPILE_STDCXX_11 (#756035) Older distributions don't include Autoconf Archive at all and newer distributions don't always include it. Therefore we have to have a local copy of the AX_CXX_COMPILE_STDCXX_11 macro with GParted. Bug 756035 - GParted does not compile with newer gtkmm libraries in Fedora 23
2015-10-04 07:39:02 -06:00
m4/*.m4
!m4/ax_cxx_compile_stdcxx_11.m4
Update Autoconf macro AX_CXX_COMPILE_STDCXX_11 to latest serial 18 Update to the latest version of the AX_CXX_COMPILE_STDCXX_11 macro from the Autoconf Archive, Note that the macro now depends on AX_CXX_COMPILE_STDCXX so this macro has to be included too.
2018-07-28 02:37:28 -06:00
!m4/ax_cxx_compile_stdcxx.m4
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
missing
mkinstalldirs
Add required polkit action file (#776437) An action file is always needed with polkit to describe the privileged actions that are available to the subject (client program). For GParted the only available action is to run the gparted shell script as root. Note that the polkit action file will be installed into location $(prefix)/share/polkit-1/actions. This is required by the GNU Coding Standards [1] and to prevent 'make distcheck' from failing [2]. However polkit only uses /usr/share/polkit-1/actions for it's action files [3]. This dilemma was discussed in this Bugzilla bug 776437 and on the general Automake discussion email list [4]. The solution is to simply document in the README file that a manual additional installation step may be required. The action file is marked as translatable with the underscore (_) of the _description and _message tags identifying the string to be translated. Use of INTLTOOL_POLICY_RULE in Makefile.am to merge translations into the polkit action file necessitates increasing the minimum version of intltool to 0.36.0 where it was first introduced in intltool.m4. This will prevent GParted building on RedHat/CentOS 5 which only has intltool 0.35.0. But that doesn't matter because RedHat/CentOS 5 reached end of life on 31st March 2017. [1] GNU Coding Standards, 7.2.5 Variables for Installation Directories https://www.gnu.org/prep/standards/standards.html#Directory-Variables [2] Automake Manual, 27.10 Installing to Hard-Coded Locations https://www.gnu.org/software/automake/manual/automake.html#Hard_002dCoded-Install-Paths "My package needs to populate the installation directory of another package at install-time. I can easily compute that installation directory in configure, but if I install files therein, 'make distcheck' fails. How else should I do?" [3] polkit(8), Declaring Actions https://www.freedesktop.org/software/polkit/docs/latest/polkit.8.html#polkit-declaring-actions "A mechanism need to declare a set of actions in order to use polkit. Actions correspond to operations that clients can request the mechanism to carry out and are defined in XML files that the mechanism installs into the /usr/share/polkit-1/actions directory." [4] Not installing to hard-coded locations vs polkit's fixed location http://lists.gnu.org/archive/html/automake/2017-08/msg00015.html Bug 776437 - GParted fails to run as root under Wayland
2017-06-24 03:39:37 -06:00
org.gnome.gparted.policy
org.gnome.gparted.policy.in
Create list of file patterns for git to ignore
2009-04-18 15:11:27 -06:00
stamp-*
Add unit test suites with initial successful dummy test (#781978) Now 'make check' will additionally build and run the test suites in the ./tests directory. Add initial always successful dummy test suite. This is done using Automake support for testing. Automake Manual, 15 Support for test suites https://www.gnu.org/software/automake/manual/automake.html#Tests ./tests/Makefile.am takes some influence from the same file in the minimal-gtest-autotools template project. https://github.com/octol/minimal-gtest-autotools/blob/654848ec0164a80f851fa80b8355099f35c025a2/tests/Makefile.am Bug 781978 - Add Google Test C++ test framework
2017-04-30 05:34:37 -06:00
test-driver
Add testbuild.sh script (#699881) For developers to build GParted in a git repository, logging the top commit and build results to testbuild.log. Intended for use with git-test-sequence to verify every change of a patch set compiles, but can be used standalone too. Example usage: git-test-sequence origin/master.. testbuild.sh Further documentation can be found on the GParted web site at page: Git Source Code Management http://www.gparted.org/git.php Closes Bug #699881 - testbuild.sh - Builds GParted logging results
2013-05-07 15:51:50 -06:00
testbuild.log
Add unit test suites with initial successful dummy test (#781978) Now 'make check' will additionally build and run the test suites in the ./tests directory. Add initial always successful dummy test suite. This is done using Automake support for testing. Automake Manual, 15 Support for test suites https://www.gnu.org/software/automake/manual/automake.html#Tests ./tests/Makefile.am takes some influence from the same file in the minimal-gtest-autotools template project. https://github.com/octol/minimal-gtest-autotools/blob/654848ec0164a80f851fa80b8355099f35c025a2/tests/Makefile.am Bug 781978 - Add Google Test C++ test framework
2017-04-30 05:34:37 -06:00
tests/*.log
tests/*.trs
tests/test-suite.log
Add unit tests for BlockSpecial constructors and internal caching (#781978) So far only includes tests of the construction of BlockSpecial objects and the interaction with the internal cache used to reduce the number of stat(2) calls. Tests have been designed to be runable by non-root users and assume as little as possible about the environment by discovering used block device names and symbolic link name. Bug 781978 - Add Google Test C++ test framework
2017-05-01 13:37:16 -06:00
tests/test_BlockSpecial
Add unit tests for PasswordRAMStore module (#795617) As noted in comments: 1) This is white box testing because it uses implementation knowledge to look through the API to the internals of the password store. 2) It is not currently possible to test that the passwords are zeroed when the store is destroyed. However zeroing of memory is being tested when individual passwords are erased. Bug 795617 - Implement opening and closing of LUKS mappings
2017-10-09 04:51:07 -06:00
tests/test_PasswordRAMStore
Add initial unit tests for PipeCapture (#777973) So far just tests sending 0 bytes and a few ASCII bytes into a pipe and that they are read correctly by the PipeCapture class. Bug 777973 - Segmentation fault on bad disk
2017-05-12 15:00:08 -06:00
tests/test_PipeCapture
Add unit test suites with initial successful dummy test (#781978) Now 'make check' will additionally build and run the test suites in the ./tests directory. Add initial always successful dummy test suite. This is done using Automake support for testing. Automake Manual, 15 Support for test suites https://www.gnu.org/software/automake/manual/automake.html#Tests ./tests/Makefile.am takes some influence from the same file in the minimal-gtest-autotools template project. https://github.com/octol/minimal-gtest-autotools/blob/654848ec0164a80f851fa80b8355099f35c025a2/tests/Makefile.am Bug 781978 - Add Google Test C++ test framework
2017-04-30 05:34:37 -06:00
tests/test_dummy
Add initial create ext2 only FileSystem interface class test (!49) This is the first step of adding testing of the derived FileSystem interface classes which call the file system specific executables. Rather than mocking command execution and returned output the tests run the real commands, effectively making this integration testing. Test case setup determines the file system supported actions using get_filesystem_support() and individual tests are skipped if a feature is not supported, just as GParted does for it's actions. Each test creates it's own sparse image file and a fresh file system, performs a test on one FileSystem interface call and deletes the image file. This makes each test independent and allows them to run as a non-root user, provided the file system command itself doesn't require root. Errors reported for a failed interface call will include the GParted OperationDetails, which in turn includes the file system specific command used and stdout and stderr from it's execution. For example, temporarily breaking the test code to create a 10 KiB image file instead of 256 MiB one produces this: $ ./test_ext2 Running main() from test_ext2.cc [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from ext2Test [ RUN ] ext2Test.Create test_ext2.cc:199: Failure Value of: s_ext2_obj->create(m_partition, m_operation_detail) Actual: false Expected: true Operation details: <b><i>mkfs.ext2 -F -L &apos;&apos; &apos;/home/centos/programming/c/gparted/tests/test_ext2.img&apos;</i></b> 00:00:00 (ERROR) <i></i> <i>mke2fs 1.42.9 (28-Dec-2013) /home/centos/programming/c/gparted/tests/test_ext2.img: Not enough space to build proposed filesystem while setting up superblock </i> [ FAILED ] ext2Test.Create (25 ms) [----------] 1 test from ext2Test (25 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test case ran. (30 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] ext2Test.Create 1 FAILED TEST $ echo $? 1 Also as Utils:: and FileSystem::execute_command() are needed, this requires linking with GParted_Core for GParted_Core::mainthread and therefore with most of the non-UI classes in gpartedbin. Closes !49 - Add file system interface tests
2019-07-17 06:08:08 -06:00
tests/test_ext2