Savane Documentation Project - Bugs: bug #2872, same naming policy/permanent link [Gna!]

Savane Documentation Project - Bugs: bug #2872, same naming policy/permanent link

Group

Main
- Main
- View Members
- Search
Download
Docs
- Browse
- Submit
- Edit
- Digest
- Export
- Search
Mailing Lists
Source Code
- Use CVS
- Browse Sources Repository
Bugs
- Browse
- Reset to all open ones
- Submit
- Digest
- Export
- View Statistics
- Search
Tasks
- Browse
- Reset to all open ones
- Submit
- Digest
- Export
- View Statistics
- Search
News
- Browse
- Atom Feed
- Submit
- Manage

Show feedback again

bug #2872: same naming policy/permanent link

Submitted by:	Mathieu Roy <yeupou>
Submitted on:	Tue 13 Sep 2005 06:50:40 AM UTC

Category:	General	Severity:	3 - Normal
Priority:	5 - Normal	Item Group:	Doc structure/organization
Status:	Need Info	Assigned to:	None
Open/Closed:	Closed

Add a New Comment (Rich Markup):

You are not logged in

Please log in, so followups can be emailed to you.

Sun 18 Sep 2005 02:58:15 PM UTC, comment #4: Thanks a lot!	Mathieu Roy <yeupou>
Sun 18 Sep 2005 02:53:06 PM UTC, comment #3: Understood, and yes, the files will stay permanently in the download area, being replaced by the newer versions. So http://dl.gna.org/savane-doc/savane-user-guide.pdf and http://dl.gna.org/savane-doc/savane-install-guide.pdf should always retrieve the latest versions. Naming policy issue is also solved	Irene Fernández <irenefm>
Sun 18 Sep 2005 01:28:44 PM UTC, comment #2: No, it's a very good policy. It's just that in packaging scripts, I'd like to add wget calls to fetch automatically the latest version. And I need to be sure the links will still works, that they are more or less permanent.	Mathieu Roy <yeupou>
Sat 17 Sep 2005 09:29:20 AM UTC, comment #1: I don't understand what you mean by permanent link? In the project's download area, only the latest versions of the docs can be found. I initially thought of keeping all versions in the download area, (naming them after version numbers) but then decided it was not really worth while. Each time I make changes to the docs in the CVS, I generate the pdf and html versions and upload them to the download area, overwriting the previous ones. I thought it was best to keep everything simple, making sure the available docs were always the latest versions, but maybe it's not such a good policy?	Irene Fernández <irenefm>
Tue 13 Sep 2005 06:50:40 AM UTC, original submission: Hello, Could we have the install guide pdf named like the user guide (with - instead of _)? And could we have permanent links, which means that we would be 100% sure that a given link for both pdf guides would work? We would like to ship these with savane, wgetting the latest version each time we repackage savane.	Mathieu Roy <yeupou>

(Note: upload size limit is set to 1024 kB, after insertion of the required escape characters.)

Attach File(s):


Comment:

No files currently attached

Depends on the following items: None found

Items that depend on this one: None found

Carbon-Copy List

-unavailable- added by irenefm (Updated the item)

-unavailable- added by yeupou (Submitted the item)

Please enter the title of George Orwell's famous dystopian book (it's a date):

Follow 3 latest changes.

Date	Changed By	Updated Field	Previous Value	Replaced By
Sun 18 Sep 2005 02:54:06 PM UTC	irenefm	Reassign Item	From group Savane Documentation Project, bugs tracker	To group Savane Documentation Project, task tracker
Sun 18 Sep 2005 02:54:05 PM UTC	irenefm	Open/Closed	Open	Closed
Sat 17 Sep 2005 09:29:20 AM UTC	irenefm	Status	None	Need Info

Show feedback again