What I really like about pmw is that it's so simple. It's a very small program but it does what is needed.

The disadvantage is that you have to learn (and remember) the language. As an intermittent user, I find this difficult, so I wrote a graphical companion program called pmwScribe that puts up a stave and lets you pin notes on it while creating a pmw file in the background. It's a bit buggy; it sometimes puts in unwanted parentheses which screw up the syntax and require a manual edit to get them out again. But it does what I want.

If you have the original 4.31 source archive, one of the SBo maintainers that has access to the SBo Sourceforce might upload it there for you for hosting, unless of course you have a Sourceforge account and one of the SBo team can give you access.

Worst case, you can use Debian's 4.30 'orig' archive and just link to it. (http://deb.debian.org/debian/pool/ma...30.orig.tar.gz)

And if you do happen to use the Debian one, you can always create a diff between 4.30 and 4.31 and apply it as a patch.

Just a couple of ideas for ya.

PS: here is another link to the 'original' 4.30 source archive:
http://ftp.fr.netbsd.org/pub/pkgsrc/...mw-4.30.tar.gz

Your Debian link doesn't work. This one does:https://cdn-aws.deb.debian.org/debian/pool/main/p/pmw.

PS: I just tried a diff between the two versions. It comes out to about 2.4M because, as well as fixing some program code, he rewrote the user manual (a full-size book in pdf format). Not very practical as a patch, is it!

I've also had a look around the Slackbuilds site, guidance notes and so on. It's all much too complicated for me. I think I'm too old for this sort of thing.

Does the ftp.fr.netbsd.org link work for you? The Debian link works fine here, but that's besides the point.

If you want, you can email me what you got (your SlackBuild and 4.31 source) and I can polish it up for you.

That's kind of you. I'll do that.

I've found what was "wrong" with your links. They are to actual tarballs, not web pages so clicking on them didn't take me anywhere. I found the downloaded files on my system afterwards.

OOPs! How do I get the files to you? The LQ email option doesn't seem to include a file attachment facility.

Check your PM.

EDIT, let me change some things. I'll email it to you again.

OK it should be good now....

So, following Willy's advice, with much labour and head-scratching, I registered on Sourceforge and created a project. I have uploaded the source tarball and it can be found here. Presumably I must now add that to my slackbuild as the source address and then go through the whole business again to register with slackbuilds.org.

I really hate the way these big sites make me feel stupid and incompetent.

SBo doesn't require you to register. Once you go to upload a SlackBuild tarball, you put in a contact email, which allows you to remove the SlackBuild before it gets approved (if you realize you butchered something and want to send an updated tarball). But the information shown on SBo about the maintainer is pulled from the $PKGNAME.info file.

If you want to be a part of the SBo mailing list, that does require registration.

2 members found this post helpful.

Thanks, that's very useful.

I just hate Sourceforge period. It is an outdated and archaic way of doing revision control/development. Not that I'm a "developer", just an end-user that has to deal with it.

I shall have to add a web page explaining how I came by the program. Otherwise someone might think I was claiming it as my own work.

OK, I added a README file. Slackbuild also submitted. Let's see how it goes.

See? You're not too old... just exercising the "small steps" caution that only comes with experience Congrats hazel.

@Hazel

But I wanted to try something new. I've never made a slackbuild before and I wanted to see if I could do it.

One thing i got from trying a slackbuild it it made me brush up on bash of which i knew next to nothing. Slackbuilds now use a standardized template but for understanding and going through the process you can have a look at : https://www.slackwiki.com/Writing_A_SlackBuild_Script

I started updating it then wondered if anyone went there these days. You can then compare to the actual slackbuild for latex here:

https://slackbuilds.org/repository/1...rch=latex2html

What I did (which is definitely not the way to do it!) was to start with an existing slackbuild and edit its various parts to suit the pmw program. So you could say I was using a template, only not an official one. Then Skaendo took it in hand and edited it into the final proper form.

1 members found this post helpful.