[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#536496: 536496: opensched: Project not loaded: Cannot open data file workplan.sched



> I cannot start opensched. From the terminal:
>
> $ opensched
> Project not loaded: Cannot open data file workplan.sched
>
> I could not find anything neither in the man page, nor on a google search.

$ opensched -h
USAGE: opensched [-d] [-v] [-h] file1 [file2 file3 ...]

It looks like file1 is not optional, though the man page implies that
it's optional.  The man page shows:

SYNOPSIS
       opensched [-d] [-v] [-h] [file...]

DESCRIPTION
       The opensched program accepts a project description file, assigns tasks
       to resources, schedules tasks  to  time  periods,  and  prints  various
       reports.

       The  user  creates a project description file, which describes what has
       to be done, who can do it, etc.

       The user runs the opensched program (perhaps using  a  Makefile).   The
       program  will  schedule any tasks that have not been assigned to people
       and time periods by the user.

Looking at the source code in main.cc, if the user doesn't specify a
filename, opensched tries to open a file called "workplan.sched", but
if the user does specify filename(s), it loads it/them.  In the man
page, after "The  user  creates a project description file, which
describes what has to be done, who can do it, etc.", I would add "If a
filename is not specified by the user, the filename is assumed to be
workplan.sched."

Version 0.4.4 was released in November 2003, and upstream now has
version opensched-xml.0.2 dated October 2006 at
http://sourceforge.net/projects/opensched/ - it might be better to
package that rather than trying to fix the present version in Debian.
However, upstream notes that "A new version of the XML adventure has
been released: opensched-xml.0.2. Now, the monthly_* commands are
replaced by XSL transformations. But take care this version is
EXPERIMENTAL. Lot of work should be done before a stable release. For
example, the XML output will probably be revisited."

Yoshio



Reply to: