[RFC] what do we do with picobsd ?

[i am cc-ing -small because they are interested, but please
keep the discussion on -current]

as the subject says...

The picobsd script in the tree at the moment is broken in
several ways. It may work on 4.x, but not on newer releases.

I have a fixed version (mostly the one i attached yesterday, with
a minor fix to handle the newer boot blocks) that works also
up to -current. Besides, it relies on ports/sysutils/makefs to build
the filesystem image so it can run without superuser privs.

I know it is not ideal to have a piece of code in the main tree
that depends on an external port. Yet, better than have it broken.

Now the options are:

1. do nothing and leave things broken;

2. commit the updated script, fix one or two sample targets,
and remove the others (all of this is in src/release/picobsd)

3. remove the entire src/release/picobsd tree and move it to
a port (question - do we want the old content of src/release/picobsd
in ports/foo/picobsd/files ? In any case, we need a place in
some repository to store these things)

Option #3 is probably the best one, except that the exact 'config'
files are strongly tied to the target source tree you are using,
at least for major releases (libraries differ, application name
change, etc) and so I'd need to modify the script to reach the
templates for RELENG_7, RELENG_6... if they are not already in the
target source tree. Also, this requires a repocopy.

However given that i don't have a lot of time at the moment,
i would compromise on option #2 for the time being, and move
to option #3 at a later (but unspecified) time.

comments ?

cheers
luigi
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Validation
    ... Yeah, I can see the simplicity advantage in script coding, but the ... In order to avoid obfuscating the data model with global validation ... A side effect of splitting it into a separate tree is that I have to ...
    (comp.databases.filemaker)
  • Re: tile treeview column numbers and resizing
    ... It's the column where 'abc' is displayed in the script below. ... To deal with this I tried to resize the first ... column but as mentioned above the tree widget column 0 seems to be the ... Also a line wrap option would be good. ...
    (comp.lang.tcl)
  • Re: [RFC] what do we do with picobsd ?
    ... The picobsd script in the tree at the moment is broken in ... I know it is not ideal to have a piece of code in the main tree ... commit the updated script, fix one or two sample targets, ... files are strongly tied to the target source tree you are using, ...
    (freebsd-current)
  • Re: [PATCH TRIVIAL] Add Intel IXP2400 & IXP2800 to PCI.ids
    ... >> This could be trivially automated to have a script ... > gregkh pulls this into his pci tree every so often, ... Do we have a way for patches to flow back into sf.net. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
    ... it's not simple enough to script. ... pt_regs have to be eyeballed and have to be poked with the compiler. ... I'm now in a position that I can just keep pulling Linus's GIT tree ... The same goes for the IRQ number itself too. ...
    (Linux-Kernel)