Debian User Forums

Just looked at:

DEB package development - few questions from newbie

I'm working my way through:

https://www.debian.org/doc/manuals/debm ... ex.en.html

I've made the "hello world" into a package and played around with the various patching techniques. I then switched to the "real project" to package and I was struck by a practical issue.

I get hold of foolib-1.0.tar.gz , I untar it and get foolib-1.0/...
I do lots of work in there and build a suitable package.

Then along comes foolib-1.1.tar.gz , I untar it and get foolib-1.1/...

Now lots of the work I did in 1.0 is applicable to 1.1, do I really create a whole new tree and start again?
Similarly, if I save all my "work" in git , then it's for the 1.0 tree and I start again with 1.1 .

Feels like an RTFM, did I miss a bit somewhere ?

I just copy the debian directory over to the new version's tree then modify it as required and use the dch command to update the changelog (helps if you have $DEBFULLNAME & $DEBEMAIL exported from ~/.profile or ~/.xsessionrc).

As a general follow-up; What is the preferred DE/WM used in Testing to develop/maintain packages?

cds60601 wrote:As a general follow-up; What is the preferred DE/WM used in Testing to develop/maintain packages?

I think there is none. Well, if you are developing some DE or WM package, obviously you need those.

cds60601 wrote:What is the preferred DE/WM used in Testing to develop/maintain packages?

TTY ftw!

Head_on_a_Stick wrote:

cds60601 wrote:What is the preferred DE/WM used in Testing to develop/maintain packages?

TTY ftw!

\

LOL - I suppose that would be true since its pretty much cli iirc

For editing and managing files, use whatever apps you're most comfortable with. The DE doesn't really do much except eat up RAM that the build might require, if it's a really heavy monster like a big web browser. Otherwise, yeah, it's command line.

You can simulate HOAS's favorite old-timey terminals with cool-retro-term, now that it's in upstream Debian. Need I mention where there are Stretch and Buster backports for it?

I have now built a full package ( Apache commons daemon ...a digression from what I want/need to build) I'll probably have some follow up questions . In terms of tools , I did it all inside Emacs. I used to take great delight in my shell history having only one command in it ... emacs, then logout.