bugGNU gettext - Bugs: bug #27281, autopoint doesn't work with cvsnt...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #27281: autopoint doesn't work with cvsnt cvs implementation

Submitter:  Arkadiusz Miskiewicz <arekm>
Submitted:  Wed 19 Aug 2009 12:57:11 PM UTC
   
 
Category:  Build Severity:  3 - Normal
Item Group:  None Status:  Fix Released
Privacy:  Public Assigned to:  haible
Open/Closed:  Closed

Sun 27 Sep 2009 09:03:57 PM UTC, comment #3: 

In the next release, gettext will support configuration options
--without-cvs and --with-git that allow to specify the format
of the archive.

> 3MB vs 350kb currently. I still went for that approach (in
> PLD/Linux) since mess with cvsnt was worse for us.


OK, you will get this result with --without-cvs.

> I'll probably look if "patch" approach won't be better (smaller size).


May be. I did not want to spend time building up a version
control system based on 'patch', because the result would be
similar to 'cvs' anyway.

Bruno Haible <haible>
Group administrator
Wed 19 Aug 2009 10:05:10 PM UTC, comment #2: 


> Can you find out what options need to be passed to the cvsnt


Unfortunately cvsnt client doesn't have options to disable locking daemon connectivity.

> This can be considered for the future.


Consider such support with ./configure switch to enable. Some people will choose cvs, some, like me, git.

Well, even having sesies of plain "patches" that would store only diffs between versions (next on top of previous one + compressed) and autopoint decompressing and applying them is much saner approach than cvs IMO.

> This would eat up too much disk space.


3MB vs 350kb currently. I still went for that approach (in PLD/Linux) since mess with cvsnt was worse for us. I'll probably look if "patch" approach won't be better (smaller size).

Arkadiusz Miskiewicz <arekm>
Wed 19 Aug 2009 09:46:27 PM UTC, comment #1: 


> autopoint script when handling archive.tar.gz doesn't really
> work with alternative implementations of cvs like
> http://www.cvsnt.org/ one.


I agree that it would be useful if it did, because when choosing
among cvs.exe from cygwin and cvs.exe from cvsnt, people will
normally prefer the latter one, since it handles CR/LF <--> NL
translation reasonably, whereas the cygwin one does not handle
it at all (AFAIR).

> $ LC_ALL=C cvs -d $(pwd) init
>  cvs init: connect to 127.0.0.1(127.0.0.1):2402 failed: Connection refused
>  cvs [init aborted]: Couldn't connect to lock server


Can you find out what options need to be passed to the cvsnt
cvs.exe program so that it can operate locally, without sockets?
And provide a patch to autopoint?

> Maybe you could switch to git?


This can be considered for the future. But for the moment, cvs
is still more wide-spread and easy to install across various
platforms.

> simply having separate tarball for each archive version.


This would eat up too much disk space. Look at the table of
sizes inside the autopoint program, and you will understand.

Bruno Haible <haible>
Group administrator
Wed 19 Aug 2009 12:57:11 PM UTC, original submission:  

autopoint script when handling archive.tar.gz doesn't really work with alternative implementations of cvs like http://www.cvsnt.org/ one.

$ LC_ALL=C cvs -d $(pwd) init
cvs init: connect to 127.0.0.1(127.0.0.1):2402 failed: Connection refused
cvs [init aborted]: Couldn't connect to lock server

That's because cvsnt registers every created repo with own deamon that's not needed when using cvsnt as client.

Maybe you could switch to git? Or better find out alternative solution like simply having separate tarball for each archive version.

Arkadiusz Miskiewicz <arekm>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by haible (Posted a comment)
  • -email is unavailable- added by arekm (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-01-04 haible StatusFixed Fix Released
    2016-11-27 haible CategoryNone Build
    2009-09-27 haible Open/ClosedOpen Closed
        StatusNeed Info Fixed
    2009-09-19 haible Assigned toNone haible
    2009-08-19 haible StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code