bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

pygnulib: code separation


From: Dmitry Selyutin
Subject: pygnulib: code separation
Date: Sat, 11 May 2013 01:54:15 +0400

Hello everyone!

Since it may be annoying to support files inside pygnulib to be the same
as in gnulib, I've thought that it may be a cool idea to separate entire
pygnulib code from gnulib. What is the proposal?

I propose to accept the following hierarchy for pygnulib:
  doc
    README
    LICENSE
    INSTALL
  python
    pygnulib
      __init__.py
      constants.py
      functions.py
      GLConfig.py
      GLEmiter.py
      GLError.py
      GLFileSystem.py
      GLImporter.py
      GLMakefileEditor.py
      GLModuleSystem.py
      GLPackage.py
      GLPackageSystem.py
      GLSystem.py
      GLTestDir.py
      GLTestFlags.py
  gnulib-tool
  install.py

Note that gnulib-tool now will be the name for the gnulib-tool.py.

What will do install.py script?

1. Copy pygnulib subdirectory to Python modules directory.
2. Clone git repository of the gnulib-tool (if directory with gnulib wasn't set
    with some option for install.py script) and move this repository to some
    directory inside user's entire machine (e.g. to /usr/share/gnulib).
    Also copy doc subdirectory to /usr/share/doc.
3. Adjust GNULIB_ROOT variable inside constants.py file to point to the copied
    (i.e. cloned and moved) gnulib git repository.
4. Copy gnulib-tool to /usr/local/bin directory.

gnulib-tool will accept a new "--fetch" function to update gnulib from git.

Such combination allows to separate gnulib files (at least before it will be
merged with gnulib original files). What do you think about it?


--
With best regards,
Dmitry Selyutin

E-mail: address@hidden
Phone: +7(985)334-07-70

reply via email to

[Prev in Thread] Current Thread [Next in Thread]