#54 Proposal: Change purpose of packages directory
Closed
opened 2 years ago by dustdfg
·
21 comments
Labels
No Label
Milestone
No Milestone
Assignee
No assignee
2 Participants
Loading...
There is no content yet.
Hello!
The packages directory now is deprecated. I want to propose you to do something with it. For example, we can delete all its content and store there packages produced between stages 2 and 1. We can do it by binding it to the "/var/cache/qi/packages" folder like sources, recipes and etc (in the "enter-chroot" file).
I do not understand what you mean by "The packages directory is now deprecated", what is deprecated?. About binding, if you refer to joining by means of mount(8), it may not be a good idea, since the packages are generated within the system. Instead there could be a dead symbolic link until the package directory is available, I'm not sure...
I do not understand, which directory you refer to useless?.
Woops!. I was trying to make quote, but instead the comment was modified. Another good reason to do it through a mailing list.
"package" directory in the root of the project tree
Bind or link the package directory is desirable, as it will help the purpose of the ISOs. At this time I can not try since I am building all the distribution or the rest against GCC11.
Sounds good. :-)
I prefer bind for consistency with other lines from "enter-chroot" script. Binding of package directory must be transparent for distribution but user that compiles all packages can see them in the /packages (/ - root of repo) instead of /OUTPUT*/**/var/cache/qi/packages
I waited for your answer because I know that I should test my commits with full compiling of all packages
Done. Could you test it?.
I know English bad so I can't understand tense but I work on it right now. I want to be absolutely sure that it works so I will test (compilation of all distribution))
Okay, I've created the empty "packages" directory now. Let me know if works for you. Thanks.
I want to compile everything from scratch so, as you know, it will take much time but I have two ideas:
1) .keep file from packages dir can be replaced by readme.md file with some information about this folder
2) /stages/2/04-iso file has a line with excluding of "/var/cache/qi/packages" directory that now will be empty. When you run stage 2 you are not in the "compiled" system so packages dir isn't mounted
Yes in fact I thought about adding a readme.
About 2) I am trying to find a way to include all the packages in the image, for a full dvd; the idea is that the included packages should not appear at the root of the live system, I wonder which is the best way now about how to put the local stored packages at the /var/cache/qi/packages for the ISO...
You can't run stage 2 when you are chrooted so /var/cache/qi/packages will be empty when you run stage 2 so excluding /var/cache/qi/packages won't have any sense
Yes.. my point was how to include the packages again for the ISO (full DVD).
I make a bind in reverse, ./packages -> /var/cache/qi/packages to compose the ISO with the binary packages for the "full" DVD.
I can't understand what you want to get.
Do you want to get live iso without packages and iso with only packages?
Do you want to get one iso with live system and packages?
We must provide:
1) A DVD (live system) with packages ("full").
2) Live system or core live system in 1 CD, packages in other CDs.
OK, in this situations we need some scripts.
In the script for the full dvd iso creation we can mount this folder again
In the script for the (core) live system iso creation we mustn't mount this folder again
It is one line for /stages/2/04-iso
Do you think to use qi's --rootdir option for creating different live images?
It works. Thank you very much