Spec URL: http://jamatos.fedorapeople.org/tex-simplecv.spec
SRPM URL: http://jamatos.fedorapeople.org/tex-simplecv-1.6-1.src.rpm
Description: The simplecv document class is intended to provide a simple yet
elegant way to write your curriculum vitae (resume). This is a
repackaging of the |cv| class that has been available with LyX for a
long time. The change of name has been made necessary by the existence
of another |cv| class on CTAN.
This package is needed since lyx no longer carries this package and users of
previous versions of lyx may use documents that require it (bug #428526).
README should be in %doc.
Also the source may change while the source name remains the same.
I don't think this is an issue, but you may want to rename it
anyway to avoid ambiguities.
Also, and more importantly, the build is missing... The
.dtx and .ins are installed, but not the .cls...
You are right, of course, on both accounts. :-)
I have uploaded a new release (2) to http://jamatos.fedorapeople.org/ with
these issues fixed. :-)
The .cls should be the only installed file.
I know that, although there are precedents. :-)
See /usr/share/texmf/ptex/platex/base/ as an example.
Initially I thought about creating a subpackage that would require tetex-doc
(or texlive-doc) and would install the processed dtx file in the same
hierarchy under tetex-doc directories, in this case:
What do you think?
I don't think it is right. The installed file should be the
pdf or dvi file. So indeed you need to do something along
Then there is the issue about what to do with the .pdf and/or
.dvi file generated, put them in %doc or in
I don't have an answer for that. Maybe worth asking on the
(In reply to comment #6)
> I don't think it is right. The installed file should be the
> pdf or dvi file.
My fault for not explaining this but believe it, or not, what I wrote above
meant exactly this. :-)
>So indeed you need to do something along
> latex simplecv.dtx
> pdflatex simplecv.dtx
> Then there is the issue about what to do with the .pdf and/or
> .dvi file generated, put them in %doc or in
> I don't have an answer for that. Maybe worth asking on the
> packaging list.
That was my question. :-)
Also sooner or later we need to develop some guidelines for (la)tex
OK, I have created a documentation subpackage.
The new release (3) has a new doc subpackage where the documentation is.
Looks like the doc location is agreed. Shouldn't texhash
be called for -doc too?
Is anything happening here? Jose, dod you have a response to the question
Patrice posed above?
Other than he is right? ;-)
I agree that texhash should be run for -doc. :-)
I added the texhash for doc too in release 4.
I the %package doc, I think it should be:
and not BuildRequires.
Also I think that the doc subpackage doesn't need the main package,
one may want to study the doc without actually installing the
Anything happening with this package?
No response; closing.
The changes are trivial and in this case the use of the bugzilla interface
becomes cumbersome. :-(
On the other hand it is the end of the second semester here and so life has been
really busy here. :-(
I would like to reopen this report for several reasons, first because it is need
in lyx and second because this should allow us to gather enough experience and
insight as to draft package guidelines for tex packages and to ease the review
of future packages.
* Thu Jun 26 2008 José Matos <jamatos[AT]fc.up.pt> - 1.6-5
- doc subpackage requires tetex-doc and no longer requires the main package.
See the package and the spec file in:
Sorry for closing, but sometimes when there's no response to pings and NEEDINFO,
closing the ticket does the trick.
I note you're not using the dist tag; you package enough things in Fedora that I
assume you can deal with the issues, but lately even experienced packagers have
run into issues caused by not using the dist tag so I would still recommend it.
But in the end it's your choice.
* source files match upstream:
* package meets naming and versioning guidelines.
* specfile is properly named, is cleanly written and uses macros consistently.
* summary is OK.
* description is OK.
* build root is OK.
* license field matches the actual license.
* license is open source-compatible.
* license text not included upstream.
* latest version is being packaged.
* BuildRequires are proper.
* %clean is present.
* package builds in mock (rawhide, x86_64).
* package installs properly.
* rpmlint is silent.
* final provides and requires are sane:
tex-simplecv = 1.6-5
tex-simplecv-doc = 1.6-5
* owns the directories it creates.
* doesn't own any directories it shouldn't.
* no duplicates in %files.
* file permissions are appropriate.
* scriptlets OK (texhash).
* code, not content.
* %docs are not necessary for the proper functioning of the package.
(In reply to comment #19)
> I note you're not using the dist tag; you package enough things in Fedora that I
> assume you can deal with the issues, but lately even experienced packagers have
> run into issues caused by not using the dist tag so I would still recommend it.
What kind of issue? It seems to me that for noarch packages like this
one no %dist is better.
There is an issue of directory dependency for the -doc subpackage.
First it seems that the location should be
Then for directory owning it should depend on texlive-texmf or on
I don't think the tetex-doc dependency is strictly needed, however, contrary
to what I imply with Comment #13.
Last think is that maybe you could use tex(latex) instead of tetex-latex
if don't target F-8.
You still have to keep the release tag different between branches; without dist
you just have to do it manually, and even experienced packagers have issues.
Especially since you generally import into devel first, but its release has to
be higher than the others.
You are absolutely correct about the doc directory; _texmf/doc/tex doesn't
actually seem to exist in the distro. I know I checked it, but
I was trusting you on the tetex-doc dependency; I honestly don't understand why
it would be necessary, but I'm not TeX expert and I figured it wouldn't really
hurt anything. I'm curious as to why you said it was necessary, though. Also,
since you seem to know more about TeX than I, are the texhash scriptlets really
necessary for the -doc package?
Did the F8 tex packages grow the tex(latex) provides? It doesn't look like it
(In reply to comment #21)
> You still have to keep the release tag different between branches; without dist
> you just have to do it manually, and even experienced packagers have issues.
> Especially since you generally import into devel first, but its release has to
> be higher than the others.
Higher or equal. But indeed, it is less easy to bump in previous
release without becoming greater than devel. However the dist really
doesn't makes sense here.
> You are absolutely correct about the doc directory; _texmf/doc/tex doesn't
> actually seem to exist in the distro. I know I checked it, but
> I was trusting you on the tetex-doc dependency; I honestly don't understand why
> it would be necessary, but I'm not TeX expert and I figured it wouldn't really
> hurt anything.
(tetex/texlive)-doc holds the texdoc utility which can be used to view docs
in the texmf tree. texlive-texmf-doc holds most of the documentation,
and the _texmf/doc/latex is owned by texlive-texmf and texlive-texmf-doc.
So the texlive-texmf or texlive-texmf-doc is in my opinion needed for
directory owning. But (tetex/texlive)-doc is less needed, in my opinion,
the doc can be viewed without texdoc.
> since you seem to know more about TeX than I, are the texhash scriptlets really
> necessary for the -doc package?
Yes, they are if in the texmf tree, since then they can be accessed
by texdoc which uses kpathsea to locate them.
> Did the F8 tex packages grow the tex(latex) provides? It doesn't look like it
> from here.
No it doesn't, but I said in Comment #20 not to do it is F-8 is
Honestly, I really meant different releases. A package this small is not going
to get the manual copy and inheritance behavior, you cannot tag the exact same
EVR into two different branches, and if you could tag them you wouldn't be able
to build them, and if you could build them bodhi wouldn't let you issue updates
for them. So I'm really not kidding, the releases will need to be different.
So that's why I just recommend using the dist tag and saving the trouble of
keeping the releases straight manually. But it's up to the maintainer, of course.
I see. Shouldn't this be considered as a bug in our infrastructure?
After hearing (reading) all the arguments I will add the dist tag, after all
this package is quite small so the space factor is not an issue here.
Up on importing I will replace the dependency on texlive-texmf-doc to guarantee
the ownership of the doc directory.
New Package CVS Request
Package Name: tex-simplecv
Short Description: LaTeX class for writing curricula vitae
Branches: F-8 F-9 EL-4 EL-5
Cvsextras Commits: yes
tex-simplecv-1.6-6.fc9.1 has been submitted as an update for Fedora 9
tex-simplecv-1.6-6.fc8 has been submitted as an update for Fedora 8
Packages built to all supported Fedora versions.
tex-simplecv-1.6-6.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
tex-simplecv-1.6-6.fc9.1 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.