Bug 830065 - Cannot 'build --publish' without including the productnumber
Summary: Cannot 'build --publish' without including the productnumber
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-08 06:49 UTC by Raymond Mancy
Modified: 2016-08-16 01:27 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-17 08:05:19 UTC
Embargoed:


Attachments (Terms of Use)

Description Raymond Mancy 2012-06-08 06:49:07 UTC
Description of problem:

It would be nice if the '--publish' option to build did not have to result in an output path that contained the productnumber. 


Version-Release number of selected component (if applicable):

2.1

How reproducible:

Always

Steps to Reproduce:
1.publican build --publish --langs en-US --formats html
2.
3.
  
Actual results:
/home/user/dev/blah/pub_doc/The_Guide/publish/en-US/MyProduct/2/html/MyTitle

Expected results:

To have an option where <productnumber> is not necessarily included.

Additional info:

It seems that somewhere along the line someone decided it would be useful to be able to build the SRPM without the version number (although perhaps they didn't think it was a good idea as they called it --short_sighted).

Something similar in this situation would be nice. Perhaps --needs_glasses ?

Comment 1 Ruediger Landmann 2013-04-17 01:41:14 UTC
Moving upstream

Comment 2 Jeff Fearn 🐞 2013-07-18 08:12:24 UTC
--publish is specifically for creating the layout used on the publican WebSites, is there any reason you can't just use tmp_dir to change where it builds and then grab the content from $tmp_dir/$lang/$format?


Note You need to log in before you can comment on or make changes to this bug.