Re: [Pkgutil-users] bldcat patch to auto-generate catalog name and GPG sign

[Peter B. <bon...@op...>]

On Mon, Jul 26, 2010 at 2:32 PM,  <ma...@pr...> wrote:
> ...all packages that do not begin with uppercase CSW will have their catalogue name taken from the package name, by stripping off the leading capital letters.

That looks good except dashes can be part of a package name but not
part of the catalog name (they can have underscores). So we need to
strip dashes to be safe.

> I have also built in support for automatically GPG signing the catalogue.  pkgutil can already check the catalogue to see if it is GPG signed, so it didn't make sense that bldcat couldn't build a signed catalogue:
>
> # bldcat --gpg .
>
> ...will run 'gpg --clearsign' on the catalogue file once it has been generated.

Great!

> I have one question.  If I run 'bldcat .' I get a catalogue file that pkgutil can use.  If I run 'bldcat some/path/to/some/directory' the resulting catalogue file cannot be used by pkgutil because the pathname has been encoded in the catalogue.  Is this a deliberate feature, or is this a bug?

I can not reproduce your problem. I did the same thing without getting
the pathname included into the filename. Can you give me the actual
command you ran and a few lines of the generated catalog?

I did, however, find that if you specify a package dir with a trailing
slash the slash is at the start of every filename. I now remove the
trailing slash from the package dir if it's there.

I have also added GNU stubs to bldcat and chkcat.

-- 
/peter