bugGNU Octave - Bugs: bug #35392, /etc/octaverc

 
 

bug #35392: /etc/octaverc

Submitted by:  Cedric <manday>
Submitted on:  Sat 28 Jan 2012 09:27:27 PM UTC  
 
Category: Configuration and Build SystemSeverity: 1 - Wish
Priority: 3 - LowItem Group: Feature Request
Status: Need InfoAssigned to: None
Originator Name: Open/Closed: Open
Release: devOperating System: Any

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

(Jump to the original submission Jump to the original submission)

Fri 09 Sep 2016 04:01:47 AM UTC, comment #9:

Should we close bugs that have no people working on them even if they are still valid?

The following bugs are all related to locations of startup configuration files and IMHO are all worth working on at some point

Mike Miller <mtmiller>
Project Administrator
Wed 07 Sep 2016 04:24:44 PM UTC, comment #8:

@Mike: The last response on this was from June 2015. Do you want to change to using sysconfdir for octaverc, or should we acknowledge that no one has had sufficient interest to implement this and close it.

Rik <rik5>
Project Administrator
Thu 04 Jun 2015 12:26:42 AM UTC, comment #7:

This bug is still actionable. There are a few open bugs all having to do with the location of startup files.

Octave currently kind of follows the gdb model, in that configs are loaded from a system-wide config file, a user config file, and a startup file in the current directory.

This bug is about moving the system-wide startup file to something like $(sysconfdir)/octave/octaverc by default, or maybe allowing it to be configured, as gdb does in its configure script. Right now it defaults to $(datadir)/octave/$(version)/m/startup/octaverc with no easy way to change that. The user can set the OCTAVE_VERSION_INITFILE enviroment variable, and that is documented, but can't be set to something else globally.

But then there is also a site configuration file that is different from the version configuration file. Should both be moved to $(sysconfdir), one or the other, or neither? Or should a startup file in $(sysconfdir) be in addition to the current startup files? Lots of options.

Updating release to dev.

Mike Miller <mtmiller>
Project Administrator
Sun 28 Dec 2014 01:46:15 AM UTC, comment #6:

Do we need to do anything here, or can we close this bug report? We won't change Octave to unilaterally place files in /etc, and there is already a workaround by setting environment variables like --sysconfdir if this is what really is required.

Rik <rik5>
Project Administrator
Mon 27 Jan 2014 04:59:24 PM UTC, comment #5:

Right, I think that is taken care of by using $(sysconfdir), which will be $(prefix)/etc by default, and most distributions automatically pass --sysconfdir=/etc to configure in their packaging infrastructure. I don't know that we need special logic to change it to /etc when $(prefix) happens to be /usr. Anyone who cares about having only non-modifiable files under /usr ought to be able to pass --sysconfdir=/etc to configure.

Using $(sysconfdir)/octave/octaverc for the site configuration file might be the best way to address this.

This could be changed along with another bug, bug #36477, which is about using XDG_CONFIG_HOME (default=~/.config) for storing user preferences. We already use ~/.config/octave for the experimental GUI qt-settings file. So ~/.config/octave/octaverc could go right alongside that nicely.

Mike Miller <mtmiller>
Project Administrator
Mon 27 Jan 2014 04:36:10 PM UTC, comment #4:

By default, everything should go under $prefix so that normal users can install Octave in directories that don't require root permissions.

Also, it is convenient to have everthing under a single $prefix directory so that removing Octave can be as simple as removing a directory tree.

If $prefix is /usr, we might put configuration files in /etc by default, but /etc should not be used if $prefix is $HOME/octave-3.8.0, for example.

John W. Eaton <jwe>
Project Administrator
Mon 27 Jan 2014 12:51:40 PM UTC, comment #3:

It appears that where to put things like startup
configuration files is as unstructured as most things
in Linux, but at least the Fedora preference seems to
be (or is becoming) to use <home dir>.local/share/...

This is for individual users. System-wide stuff goes
here and there, /etc. etc....

/etc/octave seems a good choice.

Michael Godfrey <godfrey>
Project Member
Mon 27 Jan 2014 08:16:35 AM UTC, comment #2:

Yes, I think this is a good solution. Thank you.

Cedric <manday>
Mon 27 Jan 2014 01:17:46 AM UTC, comment #1:

This can be effectively done with the current version of Octave by building like this:

Octave will then look for the version and site startup files in those directories.

Is this a valid solution for what you want?

Mike Miller <mtmiller>
Project Administrator
Sat 28 Jan 2012 09:27:27 PM UTC, original submission:

The documentation mentions only a per-user and a static configuration, but no configuration in the typical /etc directory for system wide configuration.

By convention, software should not be configured through modifying installation data in /usr, which is de facto standard for many distributions.

Therefore, octave should accept /etc/octave/(<version>|site)/startup instead of or in addition to the config in /usr

Cedric <manday>

 

(Note: upload size limit is set to 16384 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 rik5 (Posted a comment)
  • -unavailable- added by jwe (Posted a comment)
  • -unavailable- added by godfrey (Posted a comment)
  • -unavailable- added by mtmiller (Posted a comment)
  • -unavailable- added by manday (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

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

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 04 Jun 2015 12:26:42 AM UTCmtmillerCategoryInterpreter=>Configuration and Build System
      Priority5 - Normal=>3 - Low
      Release3.6.0=>dev
    Mon 27 Jan 2014 01:17:46 AM UTCmtmillerSeverity3 - Normal=>1 - Wish
      StatusNone=>Need Info
      Operating SystemGNU/Linux=>Any

    Back to the top


    Powered by Savane 3.1-cleanup1