Missing documentation for bdrv.sh

[dimkr]

No description provided.

[lakshayrohila]

I have an idea about this, which I may work upon after sometime. I just needed your assistance here. I have few questions-

• Can bdrv provide any other package manager than apt?
• Is PPM always going to be built within the puppy*.sfs? and
• Can a file in bdrv.sfs overwrite a file in puppy*.sfs?

What I think to do is add bdrv docs to a build via woof-code/support/bdrv.sh keeping the docs at woof-code/support/bdrv-docs/. bdrv.sh may then copy the docs file to bdrv dir it creates. Is my approach correct?

[dimkr]

Can bdrv provide any other package manager than apt?

Currently, no.

Is PPM always going to be built within the puppy*.sfs?

Currently, yes. I've proposed making PPM optional (and enabled by default) but other people disagree with that.

Can a file in bdrv.sfs overwrite a file in puppy*.sfs?

Yes.

What I think to do is add bdrv docs to a build via woof-code/support/bdrv.sh keeping the docs at woof-

But why add any files to the build? This issue is about the operation of bdrv.sh itself and how it works. The Synaptic documentation and the apt man page are sufficient, because that's what bdrv.sh adds to the build.

[lakshayrohila]

But why add any files to the build? This issue is about the operation of bdrv.sh itself and how it works. The Synaptic documentation and the apt man page are sufficient, because that's what bdrv.sh adds to the build.

woof-CE/woof-code/rootfs-skeleton/usr/share/doc/index.html.top

Line 53 in 0b95848

<li><a href="../../local/petget/help.htm">HOWTO use the Puppy Package Manager</a></li>

We'll at least have to change the above line so as to point to some documentation which advices the user to use apt and/or synaptic package manager for installing packages, and otherwise if they want to install some puppy packages then only use PPM. We as developers know that apt is to be used, not all the users. + some buttons in few applications open up PPM, which is completely fine, except that users need to be given some information about it.

Yes, I know that this will be just a documentation for the users, not the developers. But for the developers' documentation, I too myself will have to learn something new 😀. So maybe this is half of the docs.