Re: CVS commit: wip/pt-ttf

On Tue, Oct 02, 2012 at 11:05:47PM +0300, Mike M. Volokhov wrote:
> On Wed, Sep 26, 2012 at 9:32 AM, Thomas Klausner
> <[email protected]> wrote:
> > On Tue, Sep 25, 2012 at 09:59:32PM +0000, Mike M. Volokhov wrote:
> >> Module name:  wip
> >> Committed by: bubuchka
> >> Date:         Tue Sep 25 21:59:16 UTC 2012
> >>
> >> Modified Files:
> >>       wip/pt-ttf: distinfo
> >>
> >> Log Message:
> >> The PT Serif has been updated in place.
> >> However, accordingly to zipped files the newest version still the
> >> PT Mono and therefore no version change is requires. Weird.
> >
> > In these cases, please set DIST_SUBDIR to a new value so the package
> > still works for those who already have the old distfile.
> 
> Hi, and thanks for looking at this.
> 
> The package contents was actually modified, but no version change for
> "official" numbering was detected -- the fonts have no official
> version so I have to derive it from what stated in the TTF files and
> dates in ZIP archives.

In these cases we invent the version numbers locally; e.g.
0.0.20120925 if the files were last changed on that date.

> Moreover, the PT fonts bundle contains three zipfiles, where only a
> single one might be affected. So setting DIST_SUBDIR will lead to
> number of duplicating distfiles which I'd like to avoid (except pkgsrc
> supports individual DIST_SUBDIR for every distfile). Of course the
> package may be split on three packages as well, but IMHO it's better
> to keep the whole PT font family as a single package, despite it seem
> the most appropriate approach to a pkgsrc.

I understand that we want to avoid the duplication; so perhaps
splitting up really is the best solution.

> So how about bump the package revision and force replacement of the
> changed distfile (may be currently unimplemented in pkgrsc, but
> shouldn't be a problem)? I understand that some people may want to
> keep all distfiles, but keeping them in sync with font developers
> sounds pretty consistent as well.

There is no way to force the replacement, and doing it this way means
that bulk builds will have problems.

> Alternatively, FreeBSD ports collection is keeping all zipfiles
> locally in order to workaround the issue.

Still, without a DIST_SUBDIR they can only keep one version of the
files around. That's not a good solution if the package will be
imported to pkgsrc where there are branches and different versions
might have to exist.
 Thomas

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d