Re: [Freedos-user] DOS version control

2020-03-03 Thread Rugxulo
Hi,

On Sun, Mar 1, 2020 at 1:44 PM Matej Horvat  wrote:
>
> On Tue, 18 Feb 2020 21:39:55 +0100, C. Masloch  wrote:
> > I'd be interested in this. I'm using Mercurial for my own projects.
>
> I have put the instructions here:
>   http://matejhorvat.si/en/dos/hg/

I don't know either Python nor Mercurial. But thanks for your efforts
on this. Hope it helps somebody.
(A patch might've been simpler, no offense. I should probably mirror
this for us since I did mirror PythonD.
Or should the tires be kicked a bit more?)

BTW, just a simple remark on your notes:

>> If you use a batch file to start Mercurial, you will be unable to redirect 
>> or pipe its output, which makes
>> certain commands (such as hg log) hard to use. You can use an alias if your 
>> command interpreter
>> supports it or pipe Mercurial's output to TEE inside the batch file as a 
>> workaround.

4DOS supports .BAT redirection automatically (same as XP's CMD), but
normal COMMAND.COM needs a separate shell invocation to do it:
"%COMSPEC% /c my.bat >file.out"

Is that what you meant? Does that help? Or is it more complicated?
(DJGPP would probably use its own REDIR.EXE utility, but I don't
recall if that's included in PythonD or not.)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-03-01 Thread Matej Horvat

On Tue, 18 Feb 2020 21:39:55 +0100, C. Masloch  wrote:


I'd be interested in this. I'm using Mercurial for my own projects.


I have put the instructions here:

http://matejhorvat.si/en/dos/hg/


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-20 Thread David Griffith


My reply is at the bottom.  Please put your reply there too.
On Sun, 16 Feb 2020, Andy Stamp wrote:

Hello,
I've starting working on a game and some small dual monitor (VGA + MDA)
utilities but have run into issues where the code used to work and now it
doesn't.  We use subversion, cvs, and git at work and I was wondering what
options are available for dos-based systems besides dated zip files.

Svn and git likely never had even a 386+ DOS version but I suspect that CVS
must have.  What other DOS options were used prior to the source safe era?


Check this out: 
https://retrocomputing.stackexchange.com/questions/6588/source-code-control-on-an-ms-dos-system



--
David Griffith
d...@661.org

A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-20 Thread dmccunney
On Thu, Feb 20, 2020 at 2:23 PM tom ehlert  wrote:
>
> > On 16/02/2020 22:54, tom ehlert wrote:
> >> doing programming *on* DOS in 2020 is just stupid.
>
> > Why would that be more stupid than programming *for* DOS in 2020?
> > A hobby is a hobby.
>
> ok. replace 'stupid' by 'inefficient' in the sense that there are
> easier ways to get useful DOS programs then programming on DOS itself.
> this is called cross-development.

I know a few folks who are Old Skool, and deliberately programming
*on* old DOS PCs.  It's a question of "How much performance can I
manage to coax out of ancient hardware?"  Obviously, they are hacking
in Assembler and playing with undocumented DOS functions.

Speaking personally, were I to develop for DOS, I'd *do* development
on a Windows or Linux machine, simply because of the toolchains
available on those platforms.  VCS's are a cse in point. Most
development these days uses git as the VCS, but you will never see a
git client for DOS.  I'm not sure one is possible, and even it it is,
who would build one?  And since you can develop under Windows or Linux
and cross-compile to produce a DOS executable, why would you need one?
 You won't keep your repository on the DOS PC...

But yes, we all have hobbies, and there are folks who will accept the
trade offs and live with the limitations imposed by the hardware and
OS. More power to them, but that's not where I'd invest my time.

> Tom
__
Dennis


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-20 Thread geneb

On Thu, 20 Feb 2020, tom ehlert wrote:




On 16/02/2020 22:54, tom ehlert wrote:

doing programming *on* DOS in 2020 is just stupid.



Why would that be more stupid than programming *for* DOS in 2020?
A hobby is a hobby.


ok. replace 'stupid' by 'inefficient' in the sense that there are
easier ways to get useful DOS programs then programming on DOS itself.
this is called cross-development.

I would suspect that if folks are writing new software for DOS, they're 
also after the experience.  Any idiot can cross-develop. ;)


g.

--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.diy-cockpits.org/coll - Go Collimated or Go Home.
Some people collect things for a hobby.  Geeks collect hobbies.

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://scarlet.deltasoft.com - Get it _today_!


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-20 Thread tom ehlert


> On 16/02/2020 22:54, tom ehlert wrote:
>> doing programming *on* DOS in 2020 is just stupid.

> Why would that be more stupid than programming *for* DOS in 2020?
> A hobby is a hobby.

ok. replace 'stupid' by 'inefficient' in the sense that there are
easier ways to get useful DOS programs then programming on DOS itself.
this is called cross-development.

Tom



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-20 Thread Mateusz Viste

On 16/02/2020 22:54, tom ehlert wrote:

doing programming *on* DOS in 2020 is just stupid.


Why would that be more stupid than programming *for* DOS in 2020?
A hobby is a hobby.

Mateusz


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-20 Thread tom ehlert


> I've starting working on a game and some small dual monitor (VGA +
> MDA) utilities but have run into issues where the code used to work
> and now it doesn't.  We use subversion, cvs, and git at work and I
> was wondering what options are available for dos-based systems besides dated 
> zip files.

just because you want to program *for* DOS this doesn't mean you have to
program *on* DOS.

develop on your preferred platform (I did and do everything on Windows XP,
but Linux or Mac is probably fine as well) with multiple huge
monitors, your favorite editor and other programming tools, 
google/git/cvs/whatever
all time around in the next window.

*test* on DOS, that's ok.

doing programming *on* DOS in 2020 is just stupid.

Tom



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-18 Thread C. Masloch
On at 2020-02-18 18:25 +0100, Matej Horvat wrote:
> I have managed to get Mercurial 3.4.2 running on DOS semi-reliably (at
> least for local use) with some modifications. I can try to reconstruct
> the steps needed if you want.

I'd be interested in this. I'm using Mercurial for my own projects.
Shameless plug: https://hg.ulukai.org/ecm/

Though I do still depend on things like bash, perl, grep, and sed, for
actually running my build scripts. But Mercurial running on a DOS would
still be good.

Regards,
ecm


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-18 Thread Matej Horvat
I have managed to get Mercurial 3.4.2 running on DOS semi-reliably (at  
least for local use) with some modifications. I can try to reconstruct the  
steps needed if you want.


There is also Prism, which was written with the explicit goal of running  
on DOS (in real mode, even), but is not complete:  
https://github.com/ArmstrongJ/prism


(I solved this problem by writing a primitive VCS myself, but it is  
currently unfinished, not publicly available, and might not ever be.)



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-16 Thread Tomas By
Hi,

CVS and RCS (at least) are available in DJGPP:

http://www.delorie.com/djgpp/

/Tomas



On Sun, 16 Feb 2020 19:26:03 +0100, Andy Stamp wrote:
> Hello,
> 
> I've starting working on a game and some small dual monitor (VGA +
> MDA) utilities but have run into issues where the code used to work
> and now it doesn't. We use subversion, cvs, and git at work and I
> was wondering what options are available for dos-based systems
> besides dated zip files. 
> Svn and git likely never had even a 386+ DOS version but I suspect
> that CVS must have. What other DOS options were used prior to the
> source safe era?
> 
> Thanks,
> --Andy


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] DOS version control

2020-02-16 Thread William Dudley
There were one or more version control systems, at least one on DOS, and
I'll try to dig up a name. I do remember using RCS and SCCS, but they might
have been on later Unix based jobs. RCS was revision control system and
SCCS stood for source code control system.

Bill Dudley


sent from my Linux phone

On Sun, Feb 16, 2020, 1:27 PM Andy Stamp  wrote:

> Hello,
>
> I've starting working on a game and some small dual monitor (VGA + MDA)
> utilities but have run into issues where the code used to work and now it
> doesn't.  We use subversion, cvs, and git at work and I was wondering what
> options are available for dos-based systems besides dated zip files.
>
> Svn and git likely never had even a 386+ DOS version but I suspect that
> CVS must have.  What other DOS options were used prior to the source safe
> era?
>
> Thanks,
> --Andy
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] DOS version control

2020-02-16 Thread Andy Stamp
Hello,

I've starting working on a game and some small dual monitor (VGA + MDA)
utilities but have run into issues where the code used to work and now it
doesn't.  We use subversion, cvs, and git at work and I was wondering what
options are available for dos-based systems besides dated zip files.

Svn and git likely never had even a 386+ DOS version but I suspect that CVS
must have.  What other DOS options were used prior to the source safe era?

Thanks,
--Andy
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user