Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 17 Oct 2017, 04:15
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Auto-build a Puppy iso; single script with optional gui
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 14 of 14 [200 Posts]   Goto page: Previous 1, 2, 3, ..., 12, 13, 14
Author Message
peebee


Joined: 21 Sep 2008
Posts: 2916
Location: Worcestershire, UK

PostPosted: Mon 25 Sep 2017, 18:42    Post subject: Re: Auto-build a Puppy iso; single script with optional gui  

wiak wrote:
Could you let me know at what stage you get asked if you want an uefi iso and I'll check into it and see if I can easily add that as an option in makepup, which is likely.
wiak

Lines 34&35 of _00build.conf set UFEI_ISO (sic) & G4DOS_ISO

+
grub2_efi64 must be "true" in /support/rootfs-packages.conf

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
Billtoo


Joined: 07 Apr 2009
Posts: 3238
Location: Ontario Canada

PostPosted: Mon 25 Sep 2017, 20:00    Post subject: Auto-build a Puppy iso; single script with optional gui  

I didn't edit any config files but when that pop up shows up in ./3builddistro-Z I must have clicked on the option to make a uefi iso,seems to me I've done that in the past and it had no effect.
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 340
Location: not Bulgaria

PostPosted: Mon 25 Sep 2017, 20:09    Post subject:  

Thanks, peebee and Billtoo. I'll look into it. Have any of you, or anyone reading this thread, any idea if woof-CE attempts to fulfill package dependencies as listed in, say, any of the Packages -*-* files? I'm wading through the code and note 0setup checks items in DISTRO_PKGS_SPEC-* do exist in the format-fixed, downloaded packet lists but haven't yet reached any code that resolves dependencies (tho haven't got far in my wading as yet). In practice, dependencies don't seem to get resolved for packages dropped into local-repositories for inclusion, which is a pity.


EDIT: I know there is CHECK_BINARY_DEPS= in _00build.conf but that doesn't seem to do it - at least not for packages dropped into local-repositories. I've already read some of the script code concerning that but I've already forgotten the details... but certainly what I've read didn't do what I would like.

I'll find out eventually if I don't get fed up reading code I expect...

wiak
Back to top
View user's profile Send private message 
sc0ttman


Joined: 16 Sep 2009
Posts: 2528
Location: UK

PostPosted: Mon 25 Sep 2017, 23:12    Post subject:  

wiak wrote:
Thanks, peebee and Billtoo. I'll look into it. Have any of you, or anyone reading this thread, any idea if woof-CE attempts to fulfill package dependencies as listed in, say, any of the Packages -*-* files? I'm wading through the code and note 0setup checks items in DISTRO_PKGS_SPEC-* do exist in the format-fixed, downloaded packet lists but haven't yet reached any code that resolves dependencies (tho haven't got far in my wading as yet). In practice, dependencies don't seem to get resolved for packages dropped into local-repositories for inclusion, which is a pity.


EDIT: I know there is CHECK_BINARY_DEPS= in _00build.conf but that doesn't seem to do it - at least not for packages dropped into local-repositories. I've already read some of the script code concerning that but I've already forgotten the details... but certainly what I've read didn't do what I would like.

I'll find out eventually if I don't get fed up reading code I expect...

wiak


If you're feeling adventurous (masochistic) you could

* install Pkg,
* copy the relevant woof repo files to your ~/.packages/ dir, (if needed)
* add the matching repo entries to ~/.pkg/sources-all, (if needed)
* cd into the local PET dir in woof,
* and do

Code:

pkg --update-sources # add ur new repos to the list!
pkg --workdir `pwd` 
for pet in *
do
pkg -ed $pet
done


EDIT: a bit safer, build the list of pets first, then do `pkg -ed "pet1 pet2 pet3"` ....

Either way should download (not install) the deps of each $pet into the current dir...

Until I implement a chroot type option in Pkg, that might (not!) work for ya...
(there will be caveats .. you might need to use --force if trying to get deps of pkgs already installed in ur host system, for example)

_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search
Back to top
View user's profile Send private message 
Moat


Joined: 16 Jul 2013
Posts: 755
Location: Mid-mitten, USA

PostPosted: Tue 26 Sep 2017, 04:50    Post subject:  

wiak wrote:
Also keeping Billtoo's suggestion in my head of looking into kernel-build automation, either as part of makepup (third tab maybe) or a separate script especially for that purpose ...


Don't know what I'm talking about, but could stemsee's auto kernel-compiling scripts be of possible value?

http://www.murga-linux.com/puppy/viewtopic.php?t=96723

Bob
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 14 of 14 [200 Posts]   Goto page: Previous 1, 2, 3, ..., 12, 13, 14
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1107s ][ Queries: 14 (0.0102s) ][ GZIP on ]