make buildiso path independent? #153

Closed
opened 2015-12-03 16:18:07 +00:00 by philm · 7 comments
philm commented 2015-12-03 16:18:07 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

We got deployiso being path independent, it can be run from anywhere.

Do we want buildiso to detect the iso-profiles, so it can be run from anywhere too?

*Created by: udeved* We got deployiso being path independent, it can be run from anywhere. Do we want buildiso to detect the iso-profiles, so it can be run from anywhere too?
philm commented 2015-12-03 23:42:17 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Would be nice to have, but how do you search for profiles and save their location for the next time?

*Created by: philmmanjaro* Would be nice to have, but how do you search for profiles and save their location for the next time?
philm commented 2015-12-03 23:53:35 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

We would be searching for a unique file in the iso-profiles, eg .manjaro-tools.
However, this doesn't play out well if we have say sonar in $HOME as well.
We could save path in new user config location.

*Created by: udeved* We would be searching for a unique file in the iso-profiles, eg .manjaro-tools. However, this doesn't play out well if we have say sonar in $HOME as well. We could save path in new user config location.
philm commented 2015-12-03 23:55:04 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: philmmanjaro

Ok, then step by step. It doesn't have to be in 0.9.15. There is no rush for it.

*Created by: philmmanjaro* Ok, then step by step. It doesn't have to be in **0.9.15**. There is no rush for it.
oberon commented 2015-12-04 02:47:14 +00:00 (Migrated from gitlab2.manjaro.org)

I agree, would be great to have! For me it would be sufficient to have a default location for iso-profiles and the option to change the path in manjaro-tools.conf manually.

I agree, would be great to have! For me it would be sufficient to have a default location for **iso-profiles** and the option to change the path in **manjaro-tools.conf** manually.
philm commented 2015-12-04 20:03:23 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

I got a working buildiso being path independent.

We should think about how to detect or tell buildiso what iso-profiles directory it is supposed to use.
The easiest would be to configure it in a variable, but I think a detection is better, that stores the path in a file, eg in $HOME/.config/manjaro-tools/iso-profiles.conf

*Created by: udeved* I got a working buildiso being path independent. We should think about how to detect or tell buildiso what iso-profiles directory it is supposed to use. The easiest would be to configure it in a variable, but I think a detection is better, that stores the path in a file, eg in $HOME/.config/manjaro-tools/iso-profiles.conf
philm commented 2015-12-05 00:18:39 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

Some thoughts.

In order to detect iso profiles repos, we need a consistent naming for repo additions.

eg
manjaro-iso-profiles
netrunner-iso-profiles
sonar-iso-profiles

I had some test, where detected repo paths are written to a $HOME/.config/manjaro-tools/$repo.conf

The difficulty is to set $repo without a consistent naming.

If we have a repo name, we could add it to manjaro-tools.conf, ie repo=manjaro, repo=netrunner, repo=sonar

*Created by: udeved* Some thoughts. In order to detect iso profiles repos, we need a consistent naming for repo additions. eg manjaro-iso-profiles netrunner-iso-profiles sonar-iso-profiles I had some test, where detected repo paths are written to a $HOME/.config/manjaro-tools/$repo.conf The difficulty is to set $repo without a consistent naming. If we have a repo name, we could add it to manjaro-tools.conf, ie repo=manjaro, repo=netrunner, repo=sonar
philm commented 2015-12-05 11:55:14 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

Ok, it now also works with any repo name.

Upon buildiso run, it tries to detect iso-profiles repos in $HOME, we can have it use /usr/share/manjaro-tools/iso-profiles if nothing is found in $HOME.
If found, it writes a $reponame.conf with run_dir=$path that is sourced.
To select repo, it has to be defined in manjaro-tools.conf.

I am tempted to merge iso branch in devel branch, since we don't use new repo structure yet, and both branches require new repo structure.

*Created by: udeved* Ok, it now also works with any repo name. Upon buildiso run, it tries to detect iso-profiles repos in $HOME, we can have it use /usr/share/manjaro-tools/iso-profiles if nothing is found in $HOME. If found, it writes a $reponame.conf with run_dir=$path that is sourced. To select repo, it has to be defined in manjaro-tools.conf. I am tempted to merge iso branch in devel branch, since we don't use new repo structure yet, and both branches require new repo structure.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tools/manjaro-tools#153
No description provided.