Thank you Julian for that complete summary. I can't think of any other
questions or scenarios to ask about.
Regards,
--
-- Grant Bowman <[EMAIL PROTECTED]>
* Julian Gilbey <[EMAIL PROTECTED]> [011128 16:06]:
> (1) libdb: Shared library packages have the major
Thank you Julian for that complete summary. I can't think of any other
questions or scenarios to ask about.
Regards,
--
-- Grant Bowman <[EMAIL PROTECTED]>
* Julian Gilbey <[EMAIL PROTECTED]> [011128 16:06]:
> (1) libdb: Shared library packages have the majo
On Wed, Nov 28, 2001 at 11:50:11AM -0800, Grant Bowman wrote:
> Hello,
>
> I have seen packages change their package names to include a version
> number. Reading the policy, there is little guidance on this subject.
> It would seem that's what Epochs are designed for. However I am aware
> there
On Wed, Nov 28, 2001 at 11:50:11AM -0800, Grant Bowman wrote:
> Hello,
>
> I have seen packages change their package names to include a version
> number. Reading the policy, there is little guidance on this subject.
> It would seem that's what Epochs are designed for. However I am aware
> ther
Hello,
I have seen packages change their package names to include a version
number. Reading the policy, there is little guidance on this subject.
It would seem that's what Epochs are designed for. However I am aware
there could be reasons for wanting to change the package name. One
reason mig
Hello,
I have seen packages change their package names to include a version
number. Reading the policy, there is little guidance on this subject.
It would seem that's what Epochs are designed for. However I am aware
there could be reasons for wanting to change the package name. One
reason mi
6 matches
Mail list logo
