On Fri, 1 Dec 1995, Alexander S A Kjeldaas wrote: > Which would give the following regexp: > > ^(.*)-([^-]*)-([^-]+).deb$ >
Actually I'd like to include architecture and executable type in there too for the binary packages: [EMAIL PROTECTED] - flatform specific [EMAIL PROTECTED] "" [EMAIL PROTECTED] "" emacs-el-19.30-2 - not platform specific manpages-1.8-1 "" regexp: ^(.*)-([^-]*)-([^-]+)(@([EMAIL PROTECTED]))?.deb$ The fourth part of the name should be an 'architecture' which doesn't need to be specified further for most applications. For starters I'd suggest the following architectures: i386-elf i386-aout alpha I'm not sure how the responsible for the different packages will look like when debian will be available on architectures they don't have access to, but if we will stay with the one-maintainer-one-package system I think it'd be an idea to split the revision number into a major and an architecture-specific version. i.e [EMAIL PROTECTED], or [EMAIL PROTECTED] regexp (for the first way of writing): ^(.*)-([^-]*)-([^-]+)(@([EMAIL PROTECTED])(-([^-]+))?)?.deb$ \1 - package name \2 - package version \3 - package revision \5 - binary architecture \7 - binary revision This regexp might be easier to read without unnessecary junk: ^.*-[^-]*-[^-]+(@[EMAIL PROTECTED](-[^-]+)?)?.deb$ For the source emacs-19.30-2.1.tar.gz should be enough.. What do you say? astor -
